Systems and methods for providing monitoring and response measures in connection with remote sites

ABSTRACT

A site monitoring system is provided including a base unit configured to be mounted to a structure of a monitored site; at least one sensor configured to monitor at least one monitored site condition; and a controller disposed within the base unit, the controller configured to receive sensor information regarding the at least one monitored site condition from the at least one sensor and to receive operation information from at least one monitored site management system. The controller is configured to process the sensor information and the operation information against predetermined monitored site parameters and to provide control instructions to the at least one monitored site management system to affect the at least one monitored site condition.

RELATED APPLICATIONS

The present application claims benefit under 35 USC 119(e) to U.S.Provisional Application Ser. No. 62/420,838, entitled “Systems andMethods for Providing Monitoring and Response Systems in Connection withRemote Sites”, filed Nov. 11, 2016, the content of which is incorporatedherein by reference.

The present application is related to U.S. Provisional PatentApplication Ser. No. 62/268,260, filed Dec. 16, 2015 and U.S. patentapplication Ser. No. 15/349,811 filed Nov. 11, 2016 and Ser. No.15/692,358, filed Aug. 31, 2017, the content of which is incorporatedherein by reference.

BACKGROUND OF THE INVENTION Field of the Invention

Aspects and embodiments disclosed herein relate generally to monitoringand response systems and methods to be used in remote locations forenhancing operations management capabilities.

Discussion of Related Art

Currently, most monitoring solutions used in building environments aremanual. Monitoring for conditions of concern is typically performedeither by observation or by use of handheld sensors with minimal loggingfeatures outside of manually recording the data. The use of themeasurement methods is sporadic and the repeatability of thesemeasurements cannot be confirmed. This data also holds little to novalue to insurance companies in the case of an accident claim. Forperiods of time, for example, after work hours, a site may be leftwithout any method of data measurement or monitoring. Wireless,stationary unit systems exist to measure specific variables, forexample, dust particulate and dangerous gasses; however, these systemsare not integrated into a seamless solution for site monitoring. Often,these systems do not provide real-time or near real-time data and do notoffer immediate or near immediate alerts of ongoing conditions.

There remains a need for an improved and more reliable system formonitoring and providing risk management of a remote site, for example,a construction site and/or an occupied building.

SUMMARY

Aspects and embodiments disclosed herein are generally directed tosystems and methods for monitoring for and responding to one or morepotential events of concern predicted or detected by monitoringenvironmental parameters using a network of portable base units eachpacked with various combinations of environmental sensors.

In accordance with one aspect, there is provided a monitoring systemincluding a base unit configured to be mounted to a structure of amonitored site; at least one sensor configured to monitor at least onemonitored site condition; and a controller disposed within the baseunit, the controller configured to receive sensor information regardingthe at least one monitored site condition from the at least one sensorand to receive operation information from at least one monitored sitemanagement system. The controller is configured to process the sensorinformation and the operation information against predeterminedmonitored site parameters and to provide control instructions to the atleast one monitored site management system to affect the at least onemonitored site condition.

The system further includes an analytic system and related softwareplatforms for processing and analyzing the sensor information from aplurality of sensors at each of the plurality of base units. Thesoftware platforms are configured to perform analytics on data sourcedfrom base units containing the plurality of sensors, databases stored inmemory, third-parties, and other source of data relevant to the site orsites being monitored. The system may further include a plurality ofexternal sensor units, sensor arrays, and other peripheral devices thatcommunicate with base units and enhance the functionality of themonitoring and response system. The system may also take actionresponsive to the information gathered, for example, the system mayactuate, deactivate, or otherwise control the operation of one or morepieces of equipment disposed on the site including alarms, lights, fans,valves, computers, cameras, intercoms, base units, sensors, sensorarrays, HVAC equipment, security equipment, fire prevention andsuppression equipment and more.

In accordance with various aspects, base units are configured to bemodular and contain customizable, swappable combinations of sensors,sensor arrays, and/or other connected peripherals. Base units arefurther configured to be removably mountable and/or permanentlyattachable to a wide variety of surfaces and objects disposed around asite such as a construction site and/or an occupied building. Themodularity and mobility of removably-attached base units allows theattached sensors to be flexibly chosen and dispersed in accordance withthe particular monitoring needs of the site or sites at issue, whilepermanently attached base units may be utilized in connection withongoing operation of various building management and security systems.

Still other aspects, embodiments, and advantages of these exemplaryaspects and embodiments, are discussed in detail below. Moreover, it isto be understood that both the foregoing information and the followingdetailed description are merely illustrative examples of various aspectsand embodiments, and are intended to provide an overview or frameworkfor understanding the nature and character of the claimed aspects andembodiments. Any embodiment disclosed herein may be combined with anyother embodiment in any manner consistent with at least one of theobjectives, aims, and needs disclosed herein, and references to “anembodiment,” “some embodiments,” “an alternate embodiment,” “variousembodiments,” “one embodiment” or the like are not necessarily mutuallyexclusive and are intended to indicate that a particular feature,structure, or characteristic described in connection with the embodimentmay be included in at least one embodiment. The appearances of suchterms herein are not necessarily all referring to the same embodiment.

BRIEF DESCRIPTION OF THE DRAWINGS

Various aspects of at least one embodiment are discussed below withreference to the accompanying figures, which are not intended to bedrawn to scale. The figures are included to provide illustration and afurther understanding of the various aspects and embodiments, and areincorporated in and constitute a part of this specification, but are notintended as a definition of the limits of the invention. In the figures,each identical or nearly identical component that is illustrated invarious figures is represented by a like numeral. For purposes ofclarity, not every component may be labeled in every figure. In thefigures:

FIG. 1A shows an illustrative diagrammatic view of an embodiment of asystem network;

FIG. 1B shows an illustrative diagrammatic view of an embodiment of asystem network including mesh network communication between a base unitand external sensor modules;

FIG. 2 shows an illustrative diagrammatic view of a block diagram ofcomponents of an embodiment of a base unit;

FIG. 3A shows an illustrative view of an embodiment of a base unit;

FIG. 3B shows another illustrative view of an embodiment of a base unit;

FIG. 3C shows another illustrative view of an embodiment of a base unit;

FIG. 3D shows another illustrative view of an embodiment of a base unit;

FIG. 4 shows an illustrative diagrammatic view of an embodiment of anexternal sensor array for use in a system disclosed herein;

FIG. 5 shows an illustrative diagrammatic view of an embodiment of anexternal sensor module for use in a system disclosed herein;

FIG. 6A shows an illustrative diagrammatic view of another embodiment ofan external sensor module for use in a system disclosed herein;

FIG. 6B shows an additional view of the sensor module of FIG. 6A;

FIG. 6C shows an additional view of the sensor module of FIG. 6A;

FIG. 6D shows an additional view of the sensor module of FIG. 6A;

FIG. 7A shows an illustrative diagrammatic view of an embodiment of agraphical zone map generated by a system disclosed herein;

FIG. 7B shows an illustrative diagrammatic view of another embodiment ofa graphical zone map generated by a system disclosed herein;

FIG. 8 shows an illustrative diagrammatic view of a graphical displaygenerated by a system disclosed herein of the time evolution of valuesof multiple monitored parameters associated with a site event;

FIG. 9 shows a flowchart describing embodiments of methods of performingsite event prediction via an analytic system as disclosed herein;

FIG. 10 shows a flowchart describing an embodiment of a method of baseunit network configuration;

FIG. 11A shows a flowchart describing an embodiment of a method ofdetecting or retrieving information via an analytic system disclosedherein that is relevant to a site or sites being monitored;

FIG. 11B shows a flowchart describing another embodiment of a method ofdetecting or retrieving information via an analytic system disclosedherein that is relevant to a site or sites being monitored;

FIG. 12 shows a flowchart describing another embodiment of a method ofdetecting or retrieving information via an analytic system disclosedherein that is relevant to a site or sites being monitored;

FIG. 13 shows an illustrative view of an embodiment of a base unit;

FIG. 14 shows an illustrative view of an embodiment of a base unit;

FIG. 15 shows an illustrative view of an embodiment of a base unit;

FIG. 16 shows a flowchart describing an embodiment of a method fordetermining an extent to which one or more sites being monitored are incompliance with one or more insurance or regulatory requirements and/orparameters;

FIG. 17 shows an illustrative view of an embodiment of a base unit;

FIG. 18 illustrates components of a computer system upon which variousmethods disclosed herein may be performed;

FIG. 19 illustrates details of an embodiment of a memory system for thecomputer system of FIG. 18;

FIG. 20 shows an illustrative view on an embodiment of a base unit;

FIG. 21A shows an illustrative view of an embodiment of a base unit;

FIG. 21B shows an additional view of the base unit of FIG. 21A;

FIG. 22A shows an illustrative diagrammatic view of an embodiment of asystem network;

FIG. 22B shows an illustrative diagrammatic view of an embodiment of asystem network including mesh network communication between a base unitand external sensor modules;

FIG. 23 shows an illustrative diagrammatic view of an embodiment of apermanent base unit external sensor array for use in a system disclosedherein;

FIG. 24 shows an illustrative diagrammatic view of an embodiment of anexternal sensor module for use in a system disclosed herein;

FIGS. 25A and 25B show an illustrative diagrammatic views of variousembodiment of an external sensor module for use in a system disclosedherein;

FIG. 26 is a flowchart illustrating embodiments of methods of performingsite event prediction via an analytic system as disclosed herein; and

FIG. 27 is a flowchart illustrating an embodiment of a method fordetermining an extent to which one or more sites being monitored are incompliance with one or more insurance or regulatory requirements and/orparameters.

DETAILED DESCRIPTION

In accordance with various aspects and embodiments, there is provided amonitoring solution having an intelligent communication interface. Themonitoring solution may provide real-time, continuous measurements ofenvironmental conditions to a nearby or remote location external to themonitoring equipment. A plurality of sensors may measure environmentalconditions. Measured data may be converted to digital data andtransmitted wirelessly or through a wired connection to a softwareplatform capable of generating quantifiable metrics a user can act upon.Users may use this data to track, trend, and predict potential points ofliability at a desired location using the monitoring solution. Locationsfor use of this system include but are not limited to constructionsites, oil rigs or refineries, mining sites, industrial settings, andrenovation work sites.

Aspects and embodiments disclosed herein relate to an environmentalmonitoring and risk mitigation system for a structure or a location ofindustrial activity. The system can generate alerts to inform a user ofexisting conditions, events, and/or damage. The system can generatewarnings to assist the user in the prevention of site damage and/or toadhere to assumed or specified requirements. Data from different sensorscan be paired together to provide more accurate readings and/or moreactionable data than possible by using sensors individually. In someembodiments, groups of data each representing different parameters maybe similarly combined to provide more accurate readings and/or moreactionable data even if one or more groups of data is collected from thesame sensor or sensor group. Analysis performed by a software platformincluded in the system can recognize trends in sensor data to producepredictions regarding future event occurrences. Analysis performed bythe software platform can recognize trends to create suggestions onbuilding performance, maintenance, climate control, air quality, and/orconstruction techniques. The system can aid the user in making quick,informed decisions and/or reduce liability. Report generation willdisplay sourced data to highlight patterns or trends identified overtime with use.

The following description is merely exemplary in nature and is notintended to limit the present disclosure, application, or uses. Itshould be understood that, throughout the drawings, correspondingreference numerals indicate like or corresponding parts and features.

FIG. 1A is a diagram of a monitoring system in accordance with anillustrative aspect of the present invention. FIG. 2 is a block diagramillustrating components that may make up a base unit 01, as well asvarious elements of the system external to the base unit 01. Portablebase unit(s) 01 communicate information, for example, sensor conditionsand/or alarm conditions, via wireless communications 02, 03 withserver(s) 04 and can be wirelessly re-programmed using over the airprogramming methods initiated by the server(s) 04. The wirelesscommunication used may illustratively be low-power wide-area network(LPWAN) 33, satellite 02, and/or cellular 03. It should be understoodthat while the following description references satellite 02, cellular03, and LPWAN 33, other wireless communication protocols, frequencies,or frequency bands may also or alternatively be used, for example, lowfrequency (LF), very high frequency (VHF), ultra high frequency (UHF),or 802.11 (and similar communications). A user can interface with one ormore servers 04 via a phone 05 or the internet 06 to manage themonitoring system (e.g., configure it and/or to receive information fromthe monitoring system, for example, sensor conditions, stored data,warnings, alarms, trends, predictions, system health or means to improvesite efficiency). The one or more servers 04 will contain and/or executevarious software packages that comprise much of the “backend”functionality of the present system.

FIG. 1B depicts one embodiment of external sensor modules 23 connectedvia a mesh network to a base unit 01. A plurality of external sensormodules 23 and/or external sensor arrays 424 may communicate with one ormore base unit(s) 01 using LPWAN, Bluetooth, ZigBee, LF, VHF, UHF,802.11, Wi-Fi, satellite, cellular network, or other wireless or wiredcommunication methods or protocols. External sensor modules 23 and/orexternal sensor arrays 424 may be located in close proximity to baseunit(s) 01 and contain specific sensors or combination of sensorsintended to monitor for specific conditions.

Responsive to analysis of input data sourced from base unit(s) 01, ordue to input data generated by user via a phone 05 or internet 06interface, one or more software platforms each running on one or moreservers 04 may wirelessly communicate a command to one or more baseunit(s) 01 to perform an action. Actions may be performed by baseunit(s) 01 or by external sensor unit(s) 23 and/or external sensorarrays 424. Certain base unit(s) 01 or external sensor unit(s) 23 and/orexternal sensor arrays 424 may be hard wired or wirelessly connected toone or more other systems within the site (e.g., an HVAC system, windowfans, temporary heating solutions, humidifiers, dehumidifiers, negativeair pressure solutions, machinery, tools, jackhammers, fire sprinklersystems, etc.) and may have the capability of regulating and/orcontrolling the one or more other systems. Actions generated orperformed by the software platform, base unit(s) 01, and external sensorunit(s) 23 and/or external sensor arrays 424 may result in theprevention or mitigation of damages to the site and on-site equipment,improvement of safety of on-site personnel, improvement of contractorlogistics, reduction of timeline, or other improved efficiencies.

In some embodiments, the system may determine or be instructed toperform an action. For example, the system may detect an elevated levelof moisture in one or more areas, zones, and/or sub-zones of a sitebeing monitored. In some embodiments, the system may be configured toperform a first action or set of actions, for example, adjusting theposition of one or more valves in one or more pipes to restrict the flowof water to said areas, zones, and/or sub-zones possessing the elevatedlevel of moisture. In certain embodiments, the system may first checkthat this behavior will not have undesired consequences on one or moreadditional actions being performed or having the potential to beperformed. For example, before adjusting the position of the one or morevalves, the system may first check to make sure that a fire has not beendetected in one or more of said areas, zones, and/or sub-zones, sincealtering the flow of water to one or more of those locations may allowthe fire to spread and cause more damage than an event associated withthe elevated level of moisture.

In some embodiments, the system may be configured to instruct workers orcontrol machinery to suspend and/or initiate one or more actions in oneor more zones or locations responsive to the analysis of input data. Forexample, the system may deactivate one or more sprinkler heads notproximate to a detected fire to avoid access water damage to the site.In another example, the system may reschedule time sensitive activitysuch as painting or pouring concrete responsive to detecting that theprevious coat or layer is not sufficiently dry or that ambientconditions are not favorable.

For example, base unit(s) 01 or external sensor(s) 23 and/or externalsensor arrays 424 may be connected to electrically motorized zonevalve(s), which are connected in-line with the site's water supply.Software platform running on server 04 or controller 18 within base unit01 may generate an alert and/or warning upon analysis of flow meter dataand subsequently wirelessly communicate a command to base unit 01 toperform the action of activating the electrically motorized zone valveto turn ON or OFF the flow of water or restrict maximum flow allowingfor prevention and mitigation of water damage.

Software platform running on server 04, or controller 18 within baseunit 01, may generate an alert and/or warning upon analysis oftemperature sensor(s) data and humidity sensor(s) data and subsequentlywirelessly communicate command to base unit 01 to perform the action ofactivating site's HVAC system, site temporary heating/cooling system,and/or humidifier/dehumidifier systems which allows for prevention andmitigation of high humidity damage, low temperature damage, mold damage,or undesirable worker conditions.

Through the use of a built-in microphone on the base units 01, acousticperformance of an enclosed area can be measured to show how noise flowsthrough a site. When a noise occurs, sound waves will propagate througha room and fixed surfaces, outward to any adjacent, open spaces. With anetwork of base units 01 throughout a site, the path that noise travelscan be mapped by focusing on the amplitude of the noise measurements andthe slight time delay that occurs as noise travels. Areas where noisepenetrates with a higher amplitude relative to other areas may indicateweak acoustic locations due to flanking noise, HVAC ductwork, or othersources of acoustic weak points. Noise information may further be usedfor security purposes such detecting and/or tracking unauthorizedactivity, for example, detecting the presence of an intruder at the siteand tracking their movements throughout.

Base unit(s) 01 may also be outfitted with one or more additionalinternal sensors 20, internal sensor arrays 24, and/or external sensorarrays 424. For example, UV sensors and/or light sensors combine datafrom these sensors with that from temperature 11 and/or humidity 10sensors to monitor the amount of daylight a space in a site receives.Fluctuations in a room's environment may determine how sunlight orrefracted light has an effect on the temperature, humidity, andenvironmental conditions of a room. By utilizing temperature andhumidity measurements, the indoor dew point can be calculated andmonitored. Dew point metrics will then be used for monitoring airquality and determining if water will condense on surfaces.

In some embodiments, an internal sensor 20, additional external sensor23, and/or internal or external sensor array 24, 424 may include one ormore infrared (IR) sensors and/or passive infrared (PIR) sensors. IR andPIR uses include, for example, detection of heat signatures foroccupancy monitoring, and detection of heat signatures for firedetection and classification.

Data collected from base unit(s) 01 can also be utilized duringenvironmental certification, for example, LEED or BREEAM. Information,for example, greenhouse gas emissions during construction can bemonitored using CO, CO₂, methane sensors, or other applicable internalsensors 20, external sensor modules 23, and/or internal or externalsensor arrays 24, 424. Minimum indoor air quality performance may becontinually monitored using dust particulate sensors, smoke detectingsensors, and/or gas sensors. Criteria focusing on water metering,whether indoor, outdoor, or building-level can be subsequently handledthrough the use of electrically motorized zone valves and flow meteringdevices. Acoustic performance and daylight/interior lighting monitoringwill be possible with onboard sensors previously highlighted.

Base unit(s) 01 or external sensor(s) 23 and/or external sensor arrays424 may be connected to air pressure regulator(s). A software platformrunning on server 04, or controller 18 within base unit 01, may generatecommand(s) upon analysis of pressure sensor data and subsequentlywirelessly (or over a wired connection) communicate a command to baseunit 01 to perform the action of regulating the activity of the airpressure regulator allowing for adherence to negative air pressureregulations.

Base unit(s) 01 or external sensor(s) 23 and/or external sensor arrays424 may be connected to on-site machinery and tools including but notlimited to jackhammer(s) and pile driver(s) and/or sources of power orpneumatic pressure for same. A software platform running on server 04,or controller 18 within base unit 01, may generate an alert and/orwarning upon analysis of accelerometer sensor or vibration sensor dataindicating the presence of vibrations at undesirable frequencies oramplitudes and subsequently wirelessly (or over a wired connection)communicate a command to base unit 01 to perform the action ofde-activating or changing a mode of operation of the on-site machineryand/or tools allowing for prevention and mitigation of structuraldamage, foundation cracking, and the like.

Base unit(s) 01 or external sensor(s) 23 and/or external sensor arrays424 may be connected to a localized water sprinkler system that may becomprised of localized electrically motorized valve(s) or switch(es)which control the flow of water on a room by room basis, regional basiswithin a site, or sprinkler head basis. A software platform running onserver 04, or controller 18 within base unit 01, may generate an alertand/or warning upon analysis of temperature sensor, smoke sensor, dustparticulate sensor, oxygen sensor, CO₂ sensor, PIR sensor, humiditysensor, VOC sensor, pressure sensor, acoustic sensor, and/oraccelerometer data indicating the presence or possibility of a fire andsubsequently wirelessly (or over a wired connection) communicate acommand to base unit 01 to perform the action of activating theelectrically motorized valve or switch to turn ON or OFF the localizedsprinkler system allowing for prevention and mitigation of fire damageand subsequent water damage. By controlling which sprinklers areactivated, water dispersal and resulting water damage may be contained.System connection to the water sprinkler system may be embodied as anexternal sensor unit 23 which replaces an existing sprinkler head, or isinserted in-line with the sprinkler system between the piping and thesprinkler head.

In some embodiments, an external sensor 23, internal sensor 20, internalsensor array 24, and/or external sensor array 424 may comprise a powersensor or power meter connected to one or more power outlets disposed atthe site being monitored. The power sensor may be in wireless or wiredcommunication with one or more base units 01 or directly to server 04and configured to measure an amount of power drawn from the one or moreoutlets being monitored. In certain embodiments, the power sensor maypossess one or more power ports allowing power to be drawn from the sitepower outlets and relayed through the power meter before being providedto a connected load. By measuring the amount of power drawn from the oneor more power outlets, the power sensor 20, 23 or array of power sensors24, 424 can detect usage and various power events, for example, a powersurge or outage. In further embodiments, power sensor may be configuredto provide surge protection responsive to a detected power surge orotherwise limit usage based on factors such as received power pricinginformation.

In certain embodiments, a base unit 01, external sensor 23, externalsensor array 424, external peripheral 30, and/or other connected sitecomponent may be communicatively coupled to one or more gateways and/orrouters 32. A gateway and/or router 32 may function as an intermediaryallowing one or two-way communication between the connected component(s)and a communications service or module such as satellite 02, cellulartower 03, server 04, additional gateway and/or router 32, and/or anothercommunications service or module. In other embodiments, a base unit 01,external sensor 23, external sensor array 424, external peripheral 30,and/or other connected site component may be in direct communicationwith a communications service or module such as satellite 02, cellulartower 03, server 04, and/or another communications service or modulewithout the use of a gateway as a communications intermediary. In someembodiments, one or more wireless repeaters may be positioned proximateto the one or more gateways 32 in order to extend the signal range ofeach of the one or more gateways. Server 04 may further be coupled toone or more application programming interfaces (APIs) 31 for buildingand/or managing the software executing on server 04.

FIG. 2 is a block diagram of one embodiment of a base unit 01. Base unit01 includes one or more controllers 18 each coupled to one or more wiredor wireless communication modules, for example, an LPWAN module 33, acellular module 16, Wi-Fi module 17, satellite module, or anycombination thereof, and a plurality of sensors including but notlimited to one or more of a microphone 07, dust particulate sensor 08,vibration sensor 09, humidity sensor 10, temperature sensor 11, strainsensor 12, and smoke detector 13. Other types of internal sensors 20 orinternal sensor arrays 24 may be similarly installed in a base unit 01and may include water sensors, light sensors, radio frequency (RF)sensors, CO₂ sensors, CO sensors, oxygen sensors, hydrogen sulfide (H₂S)sensors, methane sensors, gyroscopic sensors, accelerometers, windsensors, barometric sensors, infrared (IR) sensors, passive infrared(PIR) sensors, volatile organic compound (VOC) sensors, a compass,photodiode sensors, and/or magnetic sensors. Any combination of internalsensors 20 disclosed herein may also be installed as a group or array ofsensors 424 within said base unit 01 or outside of said base unit as anexternal sensor array.

One or more external sensors 23 and/or external sensor arrays 424 thatare not included in the standard base unit can be added as externalmodules, either through a wireless or wired connection, to measureadditional conditions or events of interest on a per application basis.External sensors 23 and/or external sensor arrays 424 can comprise anyof the internal sensor types 07-13, 20 and/or internal sensor arraytypes 24 discussed herein and/or known to those in the art. For example,base unit sensors may include temperature sensors, humidity sensors, anddust particulate sensors. Carbon dioxide (CO₂), carbon monoxide (CO),and oxygen concentrations and levels may be of interest to monitor in aconfined space on a job site, but not on the entire site. CO₂, CO, andoxygen sensors may thus be added as additional sensors in the form of amodular plugin to standard base units placed within the confined space.Similarly, any external sensor types 24 or external sensor array types424 disclosed herein may similarly be configured to be internal sensors20 or internal sensor arrays 24, respectively. Any combination ofinternal sensors 20 and/or external sensors 23 of the present disclosuremay comprise an internal and/or external sensor array 24, 424.

Wired connections may provide for communications and power to theinternal sensors 20, external sensor(s) 23, and/or sensor arrays 24,424. Internal sensor(s) 20 can include other types of sensors, forexample, water, light, radio frequency (RF), CO₂, CO, oxygen, hydrogensulfide (H₂S), methane, gyroscopic, accelerometer, strain, wind, and/orbarometric sensors or any of the sensor types mentioned herein withrespect to both internal and external sensors.

A cellular module 16 may be coupled to cellular antenna 14, a Wi-Fimodule 17 may be coupled to Wi-Fi antenna 15, and an LPWAN module 33 maybe coupled to LPWAN antenna 34. In some embodiments, one or moreadditional communications modules 35 and associated antennas 36 mayadditionally be coupled to at least one of the one or more controllers18 for providing one or two-way communications with an external clientor service. In various embodiments the base unit may comprise any or allof the preceding communication modules depending on the desiredconfiguration. In an illustrative aspect, battery 19 is a lithium ion orlithium polymer battery. Base unit 01 can be powered either by battery19 and/or by a hard wired connection to an external power supply 22.This external power supply can be a separate battery pack or a walloutlet to allow continuous power supply.

It should be understood that sensors 07, 08, 09, 10, 11, 12, 13, and 20may be any sensor suitable for detecting the condition that the sensoris to sense. Sensors may also be used in combination to generate new ormore accurate information. For example, temperature sensor 11 detectinga sudden rise in temperature may be paired with smoke detector 13detecting elevated smoke levels, humidity sensor 10 detecting loweringlevels of humidity, photodiode sensor detecting elevated levels oflight, and PIR sensor detecting elevated heat signatures to betterdetect conditions indicative of fire. In a second example, temperaturesensor 11 detecting sudden drop in temperature may be paired withhumidity sensor 10 detecting sudden rise in humidity, photodiode sensordetecting low levels of light, and PIR sensor detecting a coolenvironment to better detect mold growth conditions or conditionsindicative of water leaks. A photodiode sensor may be paired with ahumidity sensor, UV sensor, VOC sensor, and/or a temperature sensor tobetter detect undesirable worker conditions. A photodiode sensor may bepaired with a noise sensor to better detect a site intruder orintruders. A photodiode sensor may be paired with a humidity sensorand/or a temperature sensor to better detect the flashing and/orspreading of a fire. An infrared sensor, either alone or in combinationwith another sensor, may better predict a type of fire, for example,differentiating between a welding arc fire versus a smoldering fire.

One or more controllers 18 obtains input data regarding sensedconditions or parameters from sensors 07, 08, 09, 10, 11, 12, 13, and 20and sends a message via wireless communication using cellular module 16,Wi-Fi module 17, LPWAN module 33 (or a wired connection) to server 04containing data indicative of the conditions or parameters sensed by oneor more of the sensors. Controller 18 is configurable, via wirelessprogramming, to set which sensors 07, 08, 09, 10, 11, 12, 13, and 20 areactive and how frequently data regarding the sensed conditions orparameters of each sensor are transmitted to server 04. Server 04 canconfigure controller 18 via wired or wireless communication to set thesensor settings and thresholds as well as frequency, time, and contentsof controller 18 messages. For example, controller 18 may send dataregarding the sensed conditions or parameters of sensors 07, 08, and 09at a different frequency than that of sensors 10, 11, 12, 13, and 20 asdictated by server 04. Controller 18 can be configured to generatealerts and warnings, as well as to send data regarding the sensedconditions or parameters of one or more of the sensors at a setfrequency rate irrelevant of the sensed conditions or parameters.Alternatively controller 18 can be configured to send data regarding thesensed conditions or parameters of one or more of the sensors only uponthe sensed conditions or parameters being indicative of a possible eventof concern. A controller 18 may also store data and/or instructions inone or more connected sources of non-volatile memory 39 and/or volatilememory 40, for example, random access memory (RAM).

The system or a controller 18 may instruct one or more components of oneor more base units to enter various modes of operation in order to makethe system operate more efficiently. In various embodiments, the systemor controller 18 may keep one or more sensor types in an OFF state orlow power mode by default and only operate less energy or resourceintensive sensors regularly. When readings from the one or more lessenergy or resource intensive sensors indicate a possible event orpreliminary event, the system or controller 18 may permanently,temporarily, or intermittently activate or change the operating mode ofone or more of the sensors in an off state or low power mode to gatheradditional data regarding the event or preliminary event. For example,the system may keep one or more infrared sensors in an OFF state and oneor more additional sensors in an ON state, for example, a temperaturesensor and/or a smoke sensor. If and when the one or more additionalsensor readings indicate a spike in a temperature or presence of smoke,the system can activate the infrared sensor to read a temperaturegradient and more accurately confirm a suspected event such as a fire.

Alerts and/or warnings may be generated by either the base unitcontroller 18 or the software platform running on server 04 whenselected conditions exist. Select conditions may be detected throughanalysis of measurements of one or more individual sensors or sensortypes. Alerts and/or warnings generated due to analysis of temperaturesensor 11 data may be caused by the temperature of a region within thelocation being outside of one or more selected temperature ranges, thetemperature rising at a rate that could be deemed unsafe or indicativeof a fire, or temperature dropping at a rate that is undesired. Alertsand/or warnings generated due to analysis of humidity sensor 10 data maybe caused by the humidity of a region within the location being outsideof a selected humidity range or the humidity being at a level that couldcause damage to millwork or other materials.

Alerts and/or warnings generated due to analysis of dust particulatesensor 08 data may be caused by dust particulate levels of a regionwithin the location being outside of one or more selected dustparticulate ranges or dust particulate levels being in violation to OSHAor property owner protocols/requirements and/or any specifications madein contracts, agreements, or stipulations. Alerts and/or warningsgenerated due to analysis of any type of gas sensor (e.g. CO₂, CO,oxygen, H₂S, methane, propane, VOC's, etc.) data may be caused by gaslevels within a region of the location being outside of one or moreselected gas level ranges, gas levels exceeding flammable or explosivelevels or gas levels exceeding recommended levels for worker safety.

Alerts and/or warnings generated due to analysis of accelerometer orvibration sensor 09 data may be caused by vibration within a region ofthe location being outside of one or more selected vibration ranges,vibration that exceeds structural strength levels, vibration thatexceeds foundation strength levels, vibration at frequencies at abuilding or material's resonant frequency, or vibration that exceedscustomer imposed limits or that may be disruptive or dangerous tosurrounding structures. Alerts and/or warnings generated due to analysisof strain sensor 12 data may be caused by strain exerted on an object orentity being outside of one or more selected strain ranges, strainlevels which indicate the possibility of the existence or futureoccurrence of structural damage, strain levels which indicate thepossibility of the existence or future occurrence of foundation orframework damage, or strain levels which indicate the possibility of theexistence or future occurrence of roof failure or collapse.

Alerts and/or warnings generated due to analysis of fluid flow sensordata, sourced from flow sensors mounted on or in on-site piping, may becaused by flow levels being outside of one or more selected flow ranges,flow levels considered irregular based on past trends, flow beingdetected when no flow should exist and/or flow indicative of a waterleak.

Alerts and/or warnings generated due to analysis of electrical powerlevel data, electrical current data, electrical impedance data, and/orelectrical voltage data may be caused by levels being outside of one ormore selected ranges, levels considered irregular based on past trends,levels being detected when none should exist and/or levels indicative ofa power surge or electrical fire event.

The software platform running on server 04 may also be able to raisealerts due to analysis of data generated by more than one type ofsensor. Combining sensor data from several different types of sensorsmay provide for more accurate detection of certain conditions, ordetection of conditions that is not possible by using one sensorindividually.

One or more internal sensors 20, external sensors 23, and/or sensorarrays 24, 424 may be configured to detect weather data. For example,the one or more internal sensors 20, external sensors 23, and/or sensorarrays 24, 424 may include an ambient pressure sensor, humidity sensor,wind sensor, and/or other types of sensors known to those in the art fordetecting weather phenomena. The one or more internal sensors 20,external sensors 23, and/or sensor arrays 24, 424 may be disposed on theexterior of the site(s) being monitored in order to more directlycontact the environment outside of the site, such as an ambient weatherenvironment.

Data generated by accelerometer(s) or vibration sensor(s) may beanalyzed in conjunction with data generated by strain sensor(s) tomonitor, detect, or predict structural foundation damage, includingcracking or widening of existing cracks, or structural roof failure.

Data generated by accelerometer sensor(s) may be analyzed in conjunctionwith data generated by gyroscope sensor(s) and strain sensor(s) to moreaccurately monitor, detect, and/or predict building sway or vibrationlevels that may exceed structural safety levels as well as flexure ofstructural and support beams/members.

Data generated by temperature sensor(s) may be analyzed in conjunctionwith data generated by oxygen sensor(s), humidity sensor(s), smokesensor(s), dust particulate sensor(s), IR sensors, PIR sensors,photodiode sensors, CO₂ sensor(s), and/or CO sensor(s) to moreaccurately monitor, detect, and/or predict conditions indicative of fireor the potential for fire. Software system running on server 04 maytrack the spread of fire throughout a site and monitor, detect, and/orpredict the direction of propagation of the fire as well as how fast thefire will spread using related sensor data (e.g., oxygen levels,temperature levels, and/or humidity levels). A notification or othersoftware system running on server 04 may provide this information to athird party such as a fire department to allow for a more efficientresponse to the fire.

Data generated by humidity sensor(s) may be analyzed in conjunction withdata generated by temperature sensor(s), PIR sensors, and/ormicrophone(s) to more accurately monitor, detect, predict, and/or locatewater leaks or running water.

Data generated by humidity sensor(s) may be analyzed in conjunction withdata generated by temperature sensor(s), light sensor(s), IR sensors,PIR sensors, and/or ultraviolet (UV) sensor(s) to more accuratelymonitor, detect, and/or predict conditions which may support moldgrowth.

Data generated by temperature sensor(s) may be analyzed in conjunctionwith data generated by humidity sensor(s), microphone(s), lightsensor(s), UV sensor(s), PIR sensors, oxygen sensor(s), and/or carbondioxide sensor(s) to more accurately monitor, detect, and/or predictimproper seals, leaks, cracks, holes, or related damage in the buildingenvelope.

Data generated by microphone(s) may be analyzed in conjunction with datagenerated by accelerometer(s), vibration sensor(s), temperaturesensor(s), IR sensors, PIR sensors, photodiode sensors, and/or humiditysensor(s) to more accurately monitor, detect, and/or predict buildingsecurity and building surveillance.

The server 04 can analyze and record the input data from a plurality ofbase units 01 for further analysis, for example, by comparing sensorinput data throughout a larger region of a site or detecting trends insensor input conditions between multiple regions of a site or betweenseveral sites, and can generate additional alerts, warnings, or reportsthat could not be possible based off of the data from an individual baseunit 01. The server 04 can also source data to be used when performinganalytics from other input methods or sources (e.g., sources on theinternet, other API's or SDK's, and any partnering company's products).

Warnings, alerts, and reports generated by the controller 18 or theserver 04 can be used by the user to prevent and/or mitigate events thathave the potential to damage the site or cause an unsafe environment.The user and other personnel on the location (e.g., construction site,oil rig or refinery, mining location, industrial site, and/or renovationsite), or the personnel managing the location can have records ofenvironmental factors and data for recourse on possible insuranceclaims, warranty claims, equipment failures, and/or damages to the jobsite.

In some embodiments, base units 01 may further comprise one or moretransceivers 25 for communicating with an external device, for example,a worker's handset, cell phone, tablet, or other mobile electronicdevice. Transceiver 25 may be a low energy transceiver such as aBluetooth module, ZigBee module, LPWAN module, or other low or highenergy transceivers known to those in the art. Transceiver 25 may beconfigured to locate, identify, or communicate with one or more externaldevices within its signal range.

In other embodiments, base units 01 may be connected to one or moreexternal peripherals 30 including any manner of electronic, mechanical,or other device capable of being controlled by or communicating with thebase unit. An external peripheral 30 may comprise an actuator or othernon-sensor device (or array of actuators or other non-sensor devices)capable of performing an action to affect the site or environmentproximate to said base unit 01 or peripheral 30. A peripheral 30 may beconfigured to toggle one or more devices between an ON and an OFF stateor control other aspects of operation. For example, a peripheral 30 maycontrol the ON/OFF state or operating mode of one or more propaneheaters, fans, lights, humidifiers, and/or other device disposed in andaround the site being monitored. An actuator or other non-sensor device(or array of actuators or other non-sensor devices) serving the functionof a peripheral 30 as described herein may instead be disposedinternally within the housing of the base unit.

In other embodiments, base units 01 may comprise one or more userinterface (UI) elements 26 and/or physical buttons 27. UI 26 may beconfigured to display information relevant to the site or sites beingmonitored. UI 26 and/or physical button 27 may be further configured totrigger an action or omission in response to being pressed or otherwiseactivated by a user. For example, responsive to a user pressing physicalbutton 27 or UI element 26, the UI 26 and/or an external handset maydisplay a map of the site or sites being monitored along with a locationof the base unit and the worker location at that base unit, initiate acall for help, or signal an emergency at that location. A button 27 may,for example, be configured to perform a predetermined action when a userinteracts with it in a certain manner. For example, holding down aparticular button may trigger an alarm, whereas tapping the button mayopen a communications channel allowing the user to speak directly withsecurity personnel.

In some embodiments, base units 01 may comprise one or more speakers 29and/or intercoms 28. Base units in communication with one and other maytherefore be configured to function as a distributed workercommunication system using said speakers 29 and intercom 28. Theintercom system may also involve external handsets and devices alsoconnected to the base unit. The speaker 29 may also be used to playalert sounds or relay other audible information to the site. The speaker29 may also be used to locate individual devices upon user engagementwith software platform.

In various embodiments, data received by or transmitted from sensors,base units, and/or the server may be encrypted using one or more dataencryption methods. For example, data may be encrypted using block chainencryption, public key encryption, symmetric key encryption, and/or anycombination of encryption methods know to those in the art. Theencrypted data may be subsequently decrypted by the server 04,peripheral 30, other system component, and/or third-party deviceintended to decrypt the encrypted information.

In further embodiments, data received by or transmitted from sensors,base units, and/or the server may be associated with one or more piecesof metadata. For example, data received by or transmitted from sensors,base units, and/or the server may be time stamped.

In certain embodiments, a base unit may be configured to function as asite utility power hub 01 capable of providing additional power to oneor more internal or external power-intensive components. For example,the base unit 01 may be attached to site utility power instead ofrunning from a battery and contain one or more power ports that relaythe site utility power and allow one or more external power-intensivecomponents to be plugged into it. A power intensive component mayinclude a high-performance gas or dust sensor or wireless communicationsdevice such as a wireless gateway, router, or repeater.

It may be further desirable in certain embodiments to configure thisbase unit to function as a wireless communications hub 01 for variousdevices in use around the site that are not necessarily part of thepresent system. Accordingly, the base unit functioning as acommunications hub 01 may contain one or more wireless receivers,transceivers, gateways, and/or repeaters capable of providing wirelessconnectivity on various frequency bands and/or using various wirelesscommunications protocols known to those in the art. The base unitfunctioning as a communications hub 01 may further contain one or moreactive and/or passive radio-frequency identification (RFID) readers fordetecting active and/or passive RFID tags, respectively, located on ornear the site. For example, to track any equipment worth more than acertain amount a site operator may install one or more transmitters,transceivers, RFID tags, or other communicative devices known in the artto said equipment such that the base unit functioning as acommunications hub 01 may identify and/or locate the equipment over theappropriate frequency band. Such a base unit 01 may further contain oneor more power outlets configured to relay and provide site utility powerto external sensors 23, 424, peripherals 30, and/or otherpower-intensive components around the site.

A base unit may also be designed to function as a storage hub 01 and bemade significantly larger in size than a typical base unit. For example,a base unit functioning as a storage hub 01 may contain specializedcavities for storing typical base units 01, sensors 20, 23, sensorarrays 24, 424, peripherals 30, and/or other equipment leading up to adeployment of the present system at a site.

A base unit may be configured to function as a power pillar 01 thatincorporates any or all of the functionality of a site utility powerhub, wireless communications hub, and/or storage hub discussed above.The power pillar may include additional internal components including anemergency alert light, battery backup and/or uninterruptible powersupply (UPS), user interface and/or display, or other componentsenabling it to better function as a hub of power, communications, and/orstorage.

Base units 01 may be further configured to perform self-diagnosticsand/or generate reports concerning the status of connected sensors,peripherals, and other connected internal and external systemcomponents. A base unit 01 may store in its own memories 39, 40 and/orsend such diagnostic information to any connected component includinganother base unit 01 or a server 04 where it may be subsequentlyaccessed by a user or by a software component of the system. Forexample, the base unit 01 can detect and communicate informationrelating to battery status, component health, sensor health,calibration, and/or other diagnostics. The information may be sent, forexample, to a connected user's handset where they may view saidinformation, or to the server 04 where it may be stored in one or moredatabases for subsequent access. Each base unit 01, sensor 20, 23, 24,424, peripheral 30, and/or other system component may further contain aunique identifier (for example a serial number) allowing the system touniquely identify each system component in the course of performing thevarious functions disclosed herein.

In various embodiments, base units 01 may be further configured toenable the system to identify and track potential intruders or securitybreaches using the various sensor types and combinations discussedherein. For example, a combination of thermal sensors, microphones, IRsensors, and/or any of the other sensor types disclosed herein may beused to detect intruder or security related events. The base unit 01 maynotify appropriate security and/or emergency personnel (for examplepolice) responsive to detecting an intruder or other security breach.

FIGS. 3A-3D illustrate one embodiment of a base unit 01. Base unit 01has a front housing surface 310 and a lateral housing surface 320.

As shown in FIG. 3A, lateral housing surface 320 may be continuousforming a rectangular base. Continuous lateral housing surface 320 maytake on any number of shapes consistent with a desired form of base unit01. Lateral housing surface 320 may also be segmented into one or moresecondary lateral housing surface segments 322, 323 separated by one ormore corresponding lateral housing surface edges 321. Lateral housingsurface segments 322, 323 and edges 321 may take on any number of shapesand configurations consistent with desired form of base unit 01. Lateralhousing surface 320 or surface segments 322, 323 may be composed of anymaterial or combination of materials consistent with desiredmanufacturing specifications including, but not limited to, plastic,metal, wood, polymer, natural or artificial materials and compositematerials.

Base unit 01 may optionally possess one or more lateral port surfaces313 for housing one or more groups of lateral ports 315. Lateral portsurface 313 may be recessed or embossed relative to lateral housingsurface 320 or surface segments 322, 323. Lateral ports 315 may bedisposed directly on one or more parts of lateral housing surface 320 orsurface segments 322, 323 instead of on a lateral port surface 313.Lateral ports 315 may each comprise or consist of a communication portfor communicatively coupling an external sensor or other electronicperipheral, power port for providing power to an external sensor orother electronic peripheral, or a hybrid port capable of providing bothcommunication capabilities and power. Lateral port surfaces 313 andlateral ports 315 may be composed of any material or combination ofmaterials consistent with desired manufacturing specificationsincluding, but not limited to, plastic, metal, wood, polymer, natural orartificial materials and composite materials.

Front housing surface 310 fixedly abuts and is disposed perpendicular tolateral housing surface 320 or surface segments 322, 323, opposite rearhousing surface 340. Front housing surface 310 may be fixed to lateralhousing surface 320 or surface segments 322, 323 by one or morecorresponding housing surface connectors 325, for example, screws,bolts, rivets, or other connectors known in the art. Front housingsurface 310 may be composed of any material or combination of materialsconsistent with desired manufacturing specifications including, but notlimited to, plastic, metal, wood, polymer, natural or artificialmaterials and composite materials.

In some embodiments, front housing surface may also comprise one or morefront port surfaces (not pictured) each comprising one or more frontports (not pictured). A front port surface may be recessed or embossedrelative to front housing surface 310. Front ports may be disposeddirectly on one or more parts of front housing surface instead of on afront port surface. Front ports may each comprise or consist of acommunication port for communicatively coupling an external sensor orother electronic peripheral, power port for providing power to anexternal sensor or other electronic peripheral, or a hybrid port capableof providing both communication capabilities and power.

As depicted in FIG. 3B, rear housing surface 340 fixedly abuts and isdisposed perpendicular to lateral housing surface 320 or surfacesegments 322, 323, opposite front housing surface 310. Rear housingsurface 340 may be fixed to lateral housing surface 320 or surfacesegments 322, 323 by one or more corresponding housing surfaceconnectors 325, for example, screws, bolts, rivets, or other connectorsknown in the art (not shown in figure). Rear housing surface 340 mayinstead be contiguous with or chamfered relative to lateral housingsurface 320 or surface segments 322, 323. Rear housing surface 340 maybe composed of any material or combination of materials consistent withdesired manufacturing specifications including, but not limited to,plastic, metal, wood, polymer, natural or artificial materials andcomposite materials. In some embodiments, rear housing surface 340includes one or more mounting openings 341 for coupling the base unit toa mounting piece 360. Mounting opening or openings 341 may include athreaded aperture. In certain embodiments, a mounting opening 341 mayinstead comprise a mounting protrusion instead of an opening if aprotrusion would better enable a mounting piece 360 to attach to thebase unit.

Base unit 01 may optionally possess one or more rear port surfaces 343for housing one or more groups of rear ports 345. Rear port surface 343may be recessed or embossed relative to rear housing surface 340. Rearports 345 may be disposed directly on one or more parts of rear housingsurface 340 instead of on a rear port surface 343. Rear ports 345 mayeach comprise or consist of a communication port for communicativelycoupling an external sensor or other electronic peripheral, power portfor providing power to an external sensor or other electronicperipheral, or a hybrid port capable of providing both communicationcapabilities and power. Rear port surface 343 may be composed of anymaterial or combination of materials consistent with desiredmanufacturing specifications including, but not limited to, plastic,metal, wood, polymer, natural or artificial materials and compositematerials. Port surfaces and ports may be similarly disposed on thefront housing surface 310 instead of rear housing surface 340 or lateralhousing surface 320 or surface segments 322-323.

As depicted in FIGS. 3A and 3B, front housing surface 310 may compriseone or more primary apertures 311 each optionally covered by, fittedwith, or integral with one or more primary aperture gratings 312.Although in this embodiment primary apertures 311 are only depicted onfront housing surface 310, lateral housing surface 320 or surfacesegments 322, 323 or rear housing surface 340 may also comprise one ormore primary apertures 311, which may each optionally be covered by,fitted with, or integral with one or more primary aperture gratings 312.A primary aperture 311 may, for example, function as a vent or filter toallow and/or restrict various types or quantities of air or othergasses, particles, and/or moisture from entering the base unit 01.

Base unit 01 may possess one or more cavities 356 for removablydisposing sensors and/or sensor arrays each communicatively coupled tothe controller 18 or other base unit 01 component. In some embodiments,all or part of a cavity 356 may abut all or part of a primary aperture311. In FIG. 3B sensor hatch 350 is depicted as being disposed on rearhousing surface 340, however one or more sensor hatches 350 may bedisposed on front housing surface 310, or on lateral housing surface 320or surface segments 322, 323. Sensor hatches 350 may be removablymounted to the corresponding housing via one or more sensor hatchconnectors 351, but may also be removably mounted via another meansincluding, but not limited to, a hinge, rivet, screw, latch, or othersimilar fastening means well known to those in the art. Sensor hatches350 may also be connected to a pressure sensor, button, or other sensingmechanism to detect when the hatch or cavity is open or closed, and/orto what extent the hatch or cavity is open or closed.

In some embodiments, one or more mounting openings 341 may bealternatively or additionally located on the front housing surface 310,lateral housing surface 320, one or more lateral housing surfacesegments 322, 323, and/or other base unit surfaces.

As depicted in FIGS. 3C and 3D, a housing surface of base unit 310 maybe attached to one or more mounting pieces 360 or similar components. Insome embodiments, a mounting piece 360 may attach to the base unit via aconnection with one or more mounting openings 341 or similar connectingmeans known to those in the art. For example, mounting piece 360 mayinclude a threaded connector that screws into a mounting opening 341. Inother embodiments, a mounting piece 360 attaches directly to a housingsurface of the base unit. Mounting piece 360 may alternatively comprisea bracket, brace, connector, fastener, magnet, clip, or other securingmeans known to those in the art for removably fastening base unit to anexternal surface or structure. Mounting piece 360 may removably attachto a portion of a site surface or support structure including, but notlimited to, walls, pipes, windows, and other site surfaces known tothose in the art. In some embodiments, removably attached means able toalternate between being removed and reattached without causing anydamage or any substantial damage to the surface or structure on whichthe base unit is being mounted. Mounting piece 360 may attach to asupport structure 370, for example, a stand or tripod, either portableor fixed.

FIG. 4 depicts a collection of external sensor modules forming anexternal sensor array 424 that may contain humidity sensor(s), moisturesensor(s), and/or water contact sensor(s) intended to monitor for thespecific condition of water ingress within an exterior wall of abuilding. Illustratively, the sensor array 424 is deployed surrounding awindow frame, within the wall. It should be understood that while thefollowing description references deployment surrounding a window frame,the sensor array 424 may be placed in any location. Data from humiditysensor(s), moisture sensor(s), and/or water contact sensor(s) may beprocessed by a microprocessor and wirelessly (or by a wired connection)transmitted to a base unit 01, and further wirelessly (or by a wiredconnection) transmitted to the server 04, analytic system, and/oradditional software platform.

A further embodiment of an internal sensor 20, external sensor module23, and/or sensor array 24, 424 may contain temperature sensor(s)intended to monitor for the specific condition of pipe freezing within awall of a building. The external sensor module 23 and/or external sensorarray 424 may be mounted directly to water pipes within wall cavitiessuspected of having a high risk of freezing when the site is exposed tolow environmental temperatures. Data from temperature sensor(s) may beprocessed by a microprocessor and wirelessly transmitted to a base unit01, and further wirelessly (or by a wired connection) transmitted to theserver 04 and software platform. A third embodiment of an internalsensor 20, external sensor module 23, and/or sensor array 24, 424 maycontain temperature sensor(s) and humidity sensor(s) intended to monitorfor the specific condition of mold growth within a wall of a building.An external sensor module 23 or external sensor array 424 may be mountedwithin wall cavities suspected of having an increased risk of moldgrowth. Data from temperature sensor(s) and humidity sensor(s) may bewirelessly (or by a wired connection) transmitted to a base unit 01, andfurther wirelessly (or by a wired connection) transmitted to the server04, analytic system, and/or additional software platform. In certainembodiments, the data may first be processed by a controller ormicroprocessor embedded in or coupled to internal sensor 20, externalsensor module 23, and/or sensor array 24, 424 prior to transmission.

Internal sensor 20, external sensor module 23, and/or sensor array 24,424 may be embodied as a moisture sensor 525. FIG. 5 is a diagram of oneembodiment of a pin type moisture sensor 525 communicating with baseunit 01 via a wired connection. Moisture sensor 525 may be mountedwithin the cavity of a wall during the construction of a building, withthe pins inserted into the interior side of the building envelopesubstrate 526. Alternatively, moisture sensor 525 may be mounted withthe pins inserted into the facade 527 side of the building substrate526. A plurality of moisture sensor(s) 525 may be wired together toallow for extended moisture monitoring of one region of the substrate526.

FIGS. 6A-6D show different views of an embodiment of moisture sensor525. In this embodiment, moisture sensor 525 is a pin type moisturesensor. Pins 628 are designed with barbs to hold moisture sensor 525 insubstrate 526 after insertion, securing contact between the substrateand pins. The two pins 628 are implemented to measure the resistancethrough a specified, uniform distance of substrate, at a certain depthinto the substrate. In an alternative embodiment, four pins 628 may beused to measure moisture at two different depth levels within thesubstrate. Pins 628 may be manufactured from copper, stainless steel,titanium, or other related materials/alloys to make them resistant tocorrosion. Base section 629 of the moisture sensor 525 may be made usinga printed circuit board to hold strict tolerances of distance betweenthe pins 628 and to connect the pins 628 to external wiring. Printedcircuit board within base section 629 may contain electronics includingresistors and voltage comparator(s). Alternatively, printed circuitboard within base section 629 may contain no electronics and becomprised strictly of pins 628, internal traces, and external wiringwith secured contacts.

All circuitry needed for operation and reading of moisture sensor 525may be contained within base unit 01 or externally on the sensor cableconnecting the base section 629 to the base unit 01. This will allow themoisture sensor 525 to be cheap, disposable, and safe to be deemed a“sacrificial sensor” and permanently left within the wall cavity afterremoval of base unit 01 from the site. One embodiment of the basesection 629 will include the electrical circuitry, removing the need ofthe circuitry to be built into the base unit 01 or on an external sensorcable. Base section 629 will encapsulate all open, conductive materialexcept for pins 628, effectively making moisture sensor 525 assembly andwiring waterproof. Base section 629 and pins 628 may be designed in afashion to allow the moisture sensor 525 to be inserted into thesubstrate 526 in the same fashion as one would push a tack into atackboard.

Base unit(s) 01 may be able to detect if wireless communication to theserver 04 is interrupted or disconnected and alternatively default intoan access point mode, where nearby base unit(s) 01 may be able toconnect to each other. This will create a mesh network between localizedbase unit(s) 01, and allow for localized data processing of datagenerated by a plurality of base unit(s) 01. Data from all of the baseunit(s) 01 may be wirelessly transmitted to server 04 when one of thenow mesh network connected base unit(s) 01 regains connection to theserver 04.

Those skilled in the art will appreciate that numerous modifications andvariations may be made to the above disclosed embodiments withoutdeparting from the spirit and scope of the present invention.

FIGS. 7A and 7B depict two embodiments of graphical zone maps 700depicting one or more parameters detected by a plurality of sensorsdisposed at a monitoring site or sites. The zone maps 700 comprise agraphical representation of monitoring data shown visually in real time,near real time, or at other desired times. The maps 700 further comprisea plurality of zones 710 each corresponding to a respective area of abuilding floorplan or site map 702 and a sensing location 705. Invarious embodiments, a sensing location 705 corresponds to the locationof one or more base units 01 and/or one or more external sensors 23 orsensor arrays 24, 424 communicatively coupled to the monitoring system.In some embodiments, the size of each zone 710 may correspond to anabsolute or preferred monitoring range of the one or more base units 01and/or one or more external sensors 23 or sensor arrays 24, 424 disposedat each corresponding sensing location 705. Authorized users of themonitoring system may access a zone map via the server or an enabledbase unit, either remotely, for example, via the internet, or locallythrough a direct wired or wireless connection known to those in the art.In some embodiments, the system may be programmed determine a pluralityof zones 710 each corresponding to a sensing location 705 correspondingto one or more ranges, sensor types, or other relevant characteristicsof the one or more base units 01 and/or one or more external sensors 23or external sensor arrays 424 disposed at each corresponding sensinglocation 705, or corresponding to one or more site characteristics orsources of external information received by the analytic system asdescribed with respect to FIGS. 11A-11B and 12.

FIG. 7A depicts an embodiment of a continuous or analog zone map. Eachzone 710 corresponds to a sensing location 705 corresponding sensingequipment that includes one or more base units 01 and/or one or moreexternal sensors 23 or external sensor arrays 424 capable of detecting arange of values of one or more parameters occurring in or proximate tothe corresponding zone 710 at a certain time. For example, the sensingequipment at sensing location 705 d may be able to display a gradient ofrelative humidity (RH) values spatially distributed throughout thecorresponding zone 710 d in accordance with the legend 701. In otherembodiments, the sensing equipment disposed at a sensing location 705may be able to detect a plurality of values of a single parameterassociated with different spatial regions of the corresponding zone 710that do not correspond to a gradient or any other known pattern. In someembodiments, the sensing equipment disposed at sensing location 705 dcan depict a composite value derived from multiple sensed parametersthat represents the likelihood or other status of a specified event. Forexample, a combination of sensed humidity and temperature parameters canbe combined into a single representation of how many days until mold islikely to grow. Parameter legend 701 associates a range of color valueswith a value of a certain parameter. Parameter legend 701 mayalternatively use shading, saturation, focus, and other continuousvalues known to those in the art to identify particular values of aparameter. In some embodiments, zones of the zone map showingunacceptable or important values of a measured parameter and/orundesirable or important rates of change in a measured parameter may beidentified by blinking or other form of animation.

A sensor location 705 may further possess one or more sensor statusindicators 722 each indicating one or more statuses and/or properties ofa base unit 01, external sensor 23, or external sensor array 424corresponding to that sensing location 705. For example, a sensor statusindicator 705 may indicate that the base unit 01 located at sensinglocation 705 b has a light 37 that is turned on.

In some embodiments, a zone map may further contain one or morecomponent indicators 720 identifying said component and/or representingone or more aspects of its position or status. A component may be aperipheral 30, base unit 01 not currently being treated as a sensinglocation 705 by the current zone map, external sensor or sensor arraynot currently being treated as a sensing location 705 by the currentzone map, or other component being monitored and/or controlled by thesystem. One or more component status indicators 721 may further beincluded on the zone map indicating one or more statuses or propertiesof the associated component.

An example of sensor status indicators 722 and/or component statusindicators 721 may be an arrow representing the orientation of and/ordirection or speed of travel of the corresponding base unit, piece ofsensing equipment, or component. Other examples include statusindicators that represent an elapsed time since previous calibration,battery status indicators, and indicators of other self-diagnostic data.

The information displayed by one or more system component iconsincluding sensor locations 705, sensor status indicators 722, componentindicators 720, and/or component status indicators 721 may be furtherused to assist in calibrating system components including base units 01,sensors 20, 23, 24, 424, peripherals 30, and/or other componentscommunicatively coupled to the system. Calibration may be performedmanually by a user by adjusting an operating mode of a system componentresponsive to the information conveyed by the various system componenticons. In some embodiments, the system may be programmed to performautomatic calibration responsive to determining that one or morestatuses of one or more system components meets or exceeds one or moreknown thresholds.

FIG. 7B depicts an embodiment of a discrete zone map. Each zone 710corresponds to a sensing location 705 containing sensing equipment thatincludes one or more base units 01 and/or one or more external sensors23 or external sensor arrays 424 capable of detecting a finite amount ofvalues of one or more parameters occurring in or proximate to thecorresponding zone 710 at a certain time. For example, in the presentfigure the sensing equipment disposed at sensing location 705 f can beassigned exclusively to zone 710 f and depict the value of the parameterrepresenting how many days until mold is likely to grow within thatzone. In some embodiments, the sensing equipment disposed at sensinglocation 705 f can depict a composite value derived from multiple sensedparameters that represents the likelihood or other status of a specifiedevent. For example, a combination of sensed humidity and temperatureparameters can be combined into a single representation of how many daysuntil mold is likely to grow. In other embodiments, a zone can bedivided into one or more sub-zone, each sub-zone corresponding to itsown discrete parameter value of continuous range of parameter values.For example, the sensing equipment corresponding to sensing location 705e can be assigned exclusively to monitor zone 710 e, which is furtherdivided into first sub-zone 711 e and second sub-zone 712 e. A firstsubset of the sensing equipment corresponding to sensing location 705 ecan be assigned to monitor sub-zone 711 e, while a second subset of thesensing equipment corresponding to sensing location 705 e can beassigned to monitor sub-zone 712 e. In accordance with the legend 701,discrete zone map can simultaneously depict a different parameter valuein the first sub-zone 711 e versus the second sub-zone 712 e. In otherembodiments, multiple groups of sensing equipment, for example, thesensing equipment corresponding the sensing locations 706 g and 707 gmay be assigned to monitor a single zone, for example, zone 710 g. Asensor legend 750 may also be provided and contain identifying and/orstatus information about the types of sensors and/or base unit disposedthroughout the floorplan 702, for example, the type of each piece ofsensing equipment, whether the piece of sensing equipment is mobile orstationary, the location of each piece of sensing equipment, or anyother applicable sensing equipment characteristics.

A discrete or continuous zone map may also comprise a coverage map thatdepicts sensor deployment information without depicting any sensedparameters. For example, a coverage map may depict sensor type,location, ranges, recommended zones, and/or additional sensorcharacteristics in order to help system users develop a monitoring planand/or assess monitoring capabilities.

Any and all features described with reference to a discrete zone or mapmay be applied to a continuous zone map and vice versa whereverapplicable. Zone maps may be hybrids in which some zones are continuouswhile others are discrete with respect to any or all of parametersrepresented. Some zones may be configured to represent some parametersas continuous, but represent other parameters as discrete. Differentzones and sub-zones may be monitored by and associated with any one of abase unit, sensor, group of sensors, or any combination thereof.Although FIGS. 7A and 7B depict two-dimensional zone maps eachcorresponding to a two-dimensional floorplan, a three-dimensional zonemap may also be used corresponding to a three-dimensional representationof the site or sites being monitored. A zone map may also be provided asa simulation not corresponding to any current placement of base units toassist in simulating prospective monitoring deployments in advance.

The system may further be configured to provide a monitoring and/orcontrol interface containing text or icons representing any or all ofthe features discussed in FIGS. 7A-7B or throughout this disclosure. Themonitoring and/or control interface may allow a user to observe thestatus of and/or control the operation of one or more of said componentsresponsive to an action such as clicking on the appropriate text, link,and/or icons. For example, the system may indicate that a component ismalfunctioning and a user may click on the appropriate icon to disablesaid component. The monitoring and/or control interface may furthercontain additional features such as the option to send externalnotifications, alerts, and/or reports responsive to user action. Themonitoring and/or control interface may further permit a user tomanually control the operation of one or more base units 01, sensors andsensor arrays 20, 23, 24, 424, peripherals 30, or other componentsdisposed around the site and communicatively coupled to the presentsystem. For example, a user may learn via the monitoring interface thata connected piece of equipment was accidentally left on after theconstruction crew left and responsively use the control interface todisable said connected piece of equipment. In another example, a usermay observe via the monitoring interface that conditions indicative ofice are present and responsively increase the operation of one or moreheaters and/or fans in order to better disperse heat around one or moreareas of the site.

FIG. 8 depicts an embodiment of a graphical output produced by one ormore methods of predicting, detecting, analyzing, and/or depicting anevent based on more than one parameter, for example, a first parameter850, a second parameter 860, and a third parameter 870. The graphicaloutput, the information contained within the graphical output, and theone or more methods used to produce the graphical output may be used inconjunction with the modes of event and preliminary event prediction andresponse described, for example, in FIGS. 9, 11A-11B, and 12. In thecurrent example, a water leak event may be predicted based on atemperature parameter 850, humidity parameter 860, and a particulatelevel parameter 870.

In some embodiments, a first time 810 can be identified when thetemperature and humidity parameters begin to change at a rate indicativeof a possible water leak event and the particulate level begins to riseat a rate also consistent with a possible water leak event. A secondtime 820 can be identified after the temperate and humidity parametershave stabilized and the particulate level has stabilized. A third time830 can be identified when the temperature and humidity values begin toreturn to their previous values before time 810. And lastly, a fourthtime 840 can be identified once conditions substantially return to theirstate prior to the first time 810. This method may be applied to anytype or number of parameters capable of being monitored by the presentmonitoring system, and any type or number of times, events, orpreliminary events capable of being tracked and/or identified by thepresent monitoring system.

In some embodiments, the monitoring system may provide a graphicalreport of a complex event depicting traces of the parameters involvedand/or significant times corresponding to one or more stages of thecomplex event. As in shown in FIG. 8, the report may include an eventtimeline 806 listing and describing the significance of each significanttime. The report may further include any or all of a listing of theevent type 805, the status of any alerts sent in connection with theevent at issue 803, alert recipients 802, current event status 804, andany other visual indicators that would assist a user in identifying,monitoring, detecting, depicting, predicting, responding to, orotherwise handling an event at a site being monitored.

FIG. 9 depicts a flowchart of a method 900 of one embodiment of theanalytic portion of a monitoring system as disclosed herein performingevent prediction and response at one or more sites being monitored bythe monitoring system. Event prediction and response method 900 beginsat act 902 and involves act 904—receiving information and/or accessingthe locations, types, and other properties of the one or more sensorsconnected to or installed in the one or more base units 01 at the sitebeing monitored. The system further receives information describingcharacteristics of the site itself, including site physical layoutand/or dimensions, site environmental conditions including location,climate, or weather, selected site preferences including workercondition thresholds, and current and historical data trends, customerimposed thresholds, micro-weather station data, and/or other siteenvironmental parameters. At act 905, the system determines plausibleevents or preliminary events that are detectable at the given site basedon the information received at act 904. At act 906, the analytic systemreceives and/or accesses data tailored to the specific configuration ofthe present site or sites being monitored based on the data receivedand/or accessed.

The system may maintain one or more databases of previous monitoring andresponse operations conducted at different sites including the types andlocations of various equipment deployed at the site and informationsurrounding events, preliminary events, and/or other actions that werelogged at that site. The system may be further configured to storeadditional information in a database including site configurations andstatuses at different times, environmental statuses (for example ambientweather conditions) at different times, base unit configurations andstatuses at different times, sensor configurations and statuses atdifferent times, and/or event statuses at different times. This databasemay be used in connection with any of the data lookup or comparisonfunctions performed within the scope of this disclosure. For example,the system may associate a present site with one or more previous sitescontaining a similar physical and/or environmental layout and similarbase unit and/or sensor configuration, and predict, based on events thatwere detected at the previous sites, one or more events that are morelikely to occur at the current site. Such predictions may enhancemonitoring and/or response operations at the current site by putting thesystem and/or system users on notice of elevated sources of risk. Suchassociations may also assist system users in setting up operations at anew site and/or reconfiguring operations at an existing site. Forexample, the database associations may assist system users in selectingthe number, type, location, and/or operating mode of one or more baseunits 01, sensors and sensor arrays 20, 23, 24, 424, peripherals 30,and/or other connected system components.

Act 906 may further include generating a model of the site or sitesbased on the information received in acts 904-906. In one embodiment,the tailored data is received and/or accessed pursuant to one of thedatabase selection methods depicted in FIGS. 11A-11B, however theanalytic system may receive and/or access data used to perform eventprediction via an alternate method or source. At act 908, the analyticsystem uses the site configuration data received and/or accessed duringact 904 and the tailored data received and/or accessed during act 906 todetermine one or more parameter thresholds corresponding to one or moreevents and/or preliminary events. A preliminary event may be an eventthat may be indicative of a potential or imminent occurrence of anundesirable or important event. For example, a preliminary event may bean increase in temperature beyond a certain threshold, which may beindicative of an increased likelihood of a possible fire. In someembodiments, an event or preliminary event may be indicated by aplurality of parameter thresholds instead of a single parameterthreshold.

At act 910, the analytic system receives monitoring data from the one ormore sensors at the one or more sites. At act 912, the system comparesthe data received during the previous step to the parameter thresholdsdetermined during act 908 to determine whether an event is in progress.The analytic system may comprise a memory that stores associationsbetween certain types or configurations of parameter thresholds andcertain events and, in some embodiments, preliminary events.

In some embodiments, the event prediction and response system 900further comprises the ability to detect preliminary or suspected events.If an event is not detected, the system proceeds to act 916 to determinewhether a preliminary event is in progress based on stored associationsbetween monitoring data and various preliminary event types. If apreliminary event is not detected, the system resets, pauses, repeats orotherwise continues with its current programming depending on thedesired embodiment. If the system detects a preliminary event, at act918 the system may issue a preliminary event alert and/or takeresponsive action. For example, in some embodiments the system may becoupled to one or more actuators 30 capable of controlling the operatingmode of one or more fans disposed near one or more heaters at the sitebeing monitored. If a preliminary event is detected suggesting that coldconditions are approaching, then at act 918 the system may takeproactive/corrective action by controlling the one or more actuators 30to turn ON or increase the speed of the one or more fans located nearthe heaters in order to disperse heat at the site more effectively. Apreliminary event alert may comprise any form of alert, notification, orcommunication with an external user or entity, for example, mobile user05, desktop user 06, or other type of user or entity.

In some additional embodiments, at act 920 the system may activelymonitor and/or change the configuration, power, or other settings of oneor more sensors and/or related components and systems. In addition tostoring associations between certain types or configurations ofparameter thresholds and certain preliminary events, analytic system mayalso store associations between certain preliminary events and certainevents. The analytic system may store additional associations betweencertain parameter thresholds and certain events responsive to the one ormore events being associated with the preliminary event at issue. Usingthese associations, the analytic system can alter the programming of themonitoring system to prioritize detection of the associated events. Insome embodiments, the system may also use the associations to performadditional or different response measures at the one or more sites beingmonitored.

In one embodiment, detecting a preliminary or suspected event 916involves using one or more infrared sensors to map a gradient ofinfrared light intensity, power, energy, or a related property.Responsive to one or more infrared light properties meeting or exceedingone or more thresholds the determination that a preliminary event hasoccurred can be made and a preliminary alert or responsive action may beissued (act 918) corresponding to the type of preliminary eventinvolved.

At act 920, the system may change an operating mode or characteristic ofone or more base units, servers, handsets, sensors, actuators, and/orother system components responsive to the detection of a preliminaryevent during act 916. For example, the system may change the frequencyat which the central controller and/or base unit reads or analyzessensor data. In some embodiments, the system may change the frequency atwhich a sensor or sensors receive or transmit new data, or theconditions under which a sensor or sensors receive or transmit new data.In other embodiments, the system may change the power drawn by one ormore base units or other system components. In other embodiments, thesystem may toggle whether one or more system components are in an ONstate versus an OFF state. For example, if a preliminary eventindicating a heightened risk of fire is detected, the system mayactivate, increase the refresh frequency of, or increase the powerprovided to one or more base units and/or sensors associated with firedetection.

In some embodiments, taking responsive action during acts 914 and/or 918involves communicatively coupling one or more actuators, controllers, orother peripheral devices 30 to one or more base units. Each peripheralmay be coupled to one or more objects, devices, or systems at the siteor sites being monitored and may be configured to control one or moreaspects of operation responsive to an event determination made duringact 912 or a preliminary event determination made during acts 916, 920,and/or 922. For example, a base unit may be communicatively coupled to avalve actuator disposed in a fluid pipe and configured to control theoperation of said valve responsive to detection of a fire event. Saidactuators may be disposed within a base unit or outside of a base unitdepending on the desired configuration and type of actuator. Base unitsmay be further configured to control the operation of various types ofon-site equipment including lighting, fans, heating, humidifiers,dehumidifiers, and/or other controllable equipment or fixtures disposedin, on, or around the site(s) being monitored.

In other embodiments, taking a responsive action at acts 914 and/or 918involves automatically taking corrective or preventive action to ensurethat damage or risk from an event is minimized or avoided altogether.For example, if a motion sensor detects an event or preliminary eventcorresponding to a suspected intruder, the system may be automaticallyconfigured to activate one or more lights around the site to deter orscare off the intruder prior to initiating a full alarm or otherresponse. In another example, if a temperature sensor detects a frozenpipe, the system may be automatically configured to determine whetherincreasing the operation of one or more heaters would be sufficient tounfreeze the pipe and initiate the necessary operation of said heatersin response.

In various embodiments, the system may generate a printed, visual,audio, audiovisual, or partially printed and partially audio/visualreport responsive to the detection, suspicion, and/or conclusion of anevent and/or preliminary event. An example of a hybridprinted-audiovisual report is depicted in FIG. 8. The generation of sucha report may occur during each or any of acts 902-924.

FIG. 10 depicts a flowchart of one embodiment of a method 1000 forconfiguring a network of base units 01 within a monitoring system asdisclosed herein. The method begins at act 1002. At act 1004, a baseunit determines whether it can connect to the server 04 either directlyor via a router, gateway, or other wired or wireless mode ofcommunication known to those in the art. If so, at act 1006 the baseunit assumes a first mode of operation. If not, in some embodiments thesystem may proceed directly to act 1010 and assume a second mode ofoperation. In other embodiments, the base unit proceeds to act 1008 anddetermines whether any connections to additional base units or othernetworked devices are available. If so, at act 1012 the base unitconnects to the one or more additional base units or other networkeddevices. In some embodiments, the base unit may proceed directly to act1016 or 1020 and assume a third or fourth mode of operation,respectively.

In other embodiments, at act 1014 the base unit may determine whetherany of the additional base units are currently in a third or fourth modeof operation and responsively assume either the third or fourth mode ofoperation. In other embodiments, at act 1018, responsive to determiningthat one or more of the additional base units is or is not in a third orfourth mode of operation, the base unit may determine whether the one ormore additional base units is qualified, capable, or configured tocontrol a local network of base units. In act 1020, responsive to thedetermination in act 1018, the base unit may enter a mode of operationin which it controls a local network of base units. In act 1016,responsive to a determination in act 1018 that it is not qualified,capable, or configured to control a local network of base units, thebase unit may enter a mode of operation in which it does not control alocal network of base units. The local network may be wired, wireless,or both and may take on any number of different architectures known tothose in the art including, but not limited to, P2P and meshconfigurations. For example, in a third mode of operation the base unitmay be configured to function in a local network of base units wherein adifferent base unit has been designated as the leader or master. In someembodiments, entering a fourth mode of operation involves the base unitassuming control of a local network of multiple base units. In otherembodiments, entering a first mode of operation involves the base unitconnecting to a server capable of controlling the monitoring system. Inother embodiments, entering a second mode of operation involves the baseunit operating autonomously without connecting to a server, additionalbase unit, or other system control device.

FIGS. 11A and 11B depict flowcharts of embodiments of methods 1100 a,1100 b, respectively, for detecting and/or retrieving information usedto perform event prediction, response, and reporting as is described,for example, in FIGS. 7-9, or for another purpose involving data beingdetected or retrieved in accordance with the present disclosure.

FIG. 11A depicts a flowchart of an embodiment 1100 a of a method fordetecting and retrieving data relevant to a site or sites beingmonitored. The method begins at act 1102. In one embodiment, at act 1104the analytic system receives information identifying the locations andtypes of sensors operating at a site or sites being monitored. At act1106, the system receives any available aggregate data relevant to thesite or sites being monitored. Aggregate data may comprise preconfiguredlibraries or databases tailored to particular types of sites or sensorarrangements or drawn from a plurality of external sites or sources.Aggregate data may comprise data that has been previously processed ormanipulated to consolidate or extrapolate important values in advance ofretrieval.

At act 1108, the system retrieves any available data from asubstantially relevant site. A substantially relevant site may comprisea site possessing a similar floorplan, located in a similar environment,managed by the same owner, having the same general contractor orsubcontractor, being the same building type, possessing a similar sensorconfiguration or risk of exposure to certain events, or any other sourceof similarity that increases the likelihood that the site's informationwill be relevant to the site being monitored. At act 1110, the systemcan widen its search to retrieve data from additional sites that arerelevant to the site or sites being monitored, but to a lesser degreethan sites identified in act 1108. At act 1112, the system can furtherwiden its search to retrieve data from additional sites which were notsufficiently relevant to be included during acts 1108 or 1110. Lastly,at act 1114 the system retrieves any other relevant data available fromexternal sources not necessarily associated with site data, for example,data found on the Internet, industrial or scientific data, data sourcedfrom partner companies, weather prediction data, data owned or possessedby third-parties, and/or other sources of data relevant to determiningevents and associated parameter thresholds at the site being monitored.

After receiving the data of acts 1104-1114, at act 1116 the systemdetermines whether it can generate prediction values for any events orpreliminary events at the site or sites being monitored based on thedata received. If not, the system can proceed to act 1124 and restartthe process when desired. If so, the system can proceed to act 1120 or,in some embodiments, directly to act 1122. At act 1120 the systemproceeds to determine one or more events or preliminary events thesystem is capable of monitoring, detecting, or predicting at the site orsites being monitored based on the data received in acts 1104, 1006,1008, 1110, 1112, and/or 1114. At act 1122, the system uses thedeterminations made in the previous act to determine one or moreparameter threshold values corresponding to each event or preliminaryevent.

FIG. 11B depicts an alternate embodiment 1100 b of the method fordetecting and retrieving data relevant to a site or sites beingmonitored. Acts 1156, 1158, 1160, 1162, and 1164 are similar to acts1106, 1108, 1110, 1112, and 1114 described in FIG. 11A, respectively,however, instead of retrieving the data involved in each act, the systemaccesses all or part of the data without downloading said data in itsentirety and responsively determines whether the accessed data possessesthe desired degree of relevance to the site or sites being monitored.For example, the system may receive metadata, index, or summaryinformation describing the data, parse through all or part of the datain memory without downloading the entirety of said data to memory, orperform some other action that allows it to analyze the relevance of thedata to a particular site or sites without using as much bandwidth,power, processing capability, or other resource associated with theanalytic system as compared to the embodiment illustrated in FIG. 11A.

After determining the availability of any data in acts 1154-1164, at act1166 the system determines whether it can generate prediction values forany events or preliminary events at the site or sites being monitoredbased on the data. If not, in some embodiments the system can proceed toact 1174 and restart the process when desired. If so, at act 1168 thesystem retrieves some or all of the data determined to be available. Atact 1170 the system proceeds to associate particular data withparticular events or preliminary events. At act 1172, the system usesthe associations made in the previous step to determine one or moreparameter thresholds or patterns corresponding to each event orpreliminary event.

In various embodiments of the methods illustrated in FIGS. 11A and 11B,the system may skip any or all of acts 1106-1114, 1156-1164 depending onthe desired configuration. In the case of FIG. 11A, the system mayproceed directly from any of acts 1104, 1106, 1108, 1110, 1112, or 1114to act 1116 depending on the desired configuration. In the case of FIG.11B, the system may proceed directly from any of acts 1154, 1156, 1158,1160, 1162, or 1164 to act 1166 depending on the desired configuration.

FIG. 12 describes another embodiment 1200 of a method for detecting andretrieving data relevant to a site or sites being monitored. Acts 1206,1208, and 1210 operate similarly to acts 1106, 1108, and 1110 in FIG.11B, respectively. However, if the system determines that there isrelevant data at any of acts 1206, 1208, or 1210 it proceeds directly toone of acts 1207, 1209, or 1211, respectively, each of which operatesimilarly to act 1116 in FIGS. 11A and 11B. If an event association canbe made at that time or if the system has already reached act 1214, thesystem proceeds to act 1218, which functions similarly to act 1118 inFIG. 11B. If no event association can be made at act 1207, 1209, or1211, the system instead proceeds to one of act 1208, 1210, or 1214,respectively. Acts 1220 and 1222 function similarly to respective acts1120 and 1122 shown in FIG. 11B.

FIG. 13 illustrates another embodiment of a base unit 01. Base unit 01may have a front housing plate 1310 covering the front surface and partof the lateral surfaces. Front housing plate 1310 may also contain anyor all of the features described herein with respect to front housingsurface 310 in FIG. 3A. Base unit 01 may further have a rear housingplate 1340 covering the rear surface and all or part of the remaininglateral surfaces not covered by front housing plate 1310. In someembodiments, the lateral portions of front housing plate 1310 may abutall or part of the lateral portions of rear housing plate 1340. Rearhousing plate 1340 may also contain any or all of the features describedherein with respect to rear housing surface 340, lateral housing surface320, and/or lateral housing segments 322 and 323 as depicted in FIG. 3A.

In some embodiments, a base unit 01 may further comprise one or moresecondary apertures 1314. A secondary aperture 1314 may, for example,function as a vent or filter to allow and/or restrict various types orquantities of air or other gasses, particulates, and/or moisture fromentering the base unit 01 similar to the apertures 311. Secondaryaperture 1314 may further be covered by, fitted with, or integral withone or more secondary aperture gratings similar to sensor aperturegratings 312 depicted in FIGS. 3A and 3B.

In some embodiments, a base unit 01 may further comprise a set ofsecondary housing surfaces 1355 that are not flush with the otherhousing surfaces or plates disclosed herein. The set of secondaryhousing surfaces 1355 may abut and/or be fixedly attached to one or moreof the other housing surfaces described herein. For example, secondaryfront housing plate 1353 may abut and be fixedly attached to rearhousing plate 1340. A secondary rear housing surface 1354 is pictured inFIG. 13, however the set of secondary housing surfaces 1355 may compriseany shape and combination of front, lateral, or rear surfaces, plates,segments, and edges disclosed herein in FIGS. 3A-3D. A V-groove orU-groove 1352 may be shaped into and/or carved out from the any or allof the front, lateral, or rear surfaces, plates, segments disclosedherein in FIGS. 3A-3D and adapted to allow the base unit 01 to betterengage a secondary surface or object, for example, a pipe. For example,a V-groove or U-groove 1352 may be shaped into and carved out ofsecondary rear housing surface 1354 and secondary front housing plate1353, respectively. A mounting strap 1371 may be further attached to oneor more housing surfaces, plates, segments, and/or edges and adapted tofixedly mount the base unit 01 on a secondary object or surface, forexample, a pipe.

FIG. 14 illustrates another embodiment of a base unit 01. In someembodiments, magnet mounts 1460 may be attached a housing surface, suchas rear housing plate 1353, to allow for the base unit to be mounted toferrous material. During magnetic mounting scenarios, a detachable strap1430 may be located on the lateral face of base unit, or on or alongother faces of the base unit depending on the desired configuration. AV-groove or U-groove 1352 may be carved out of secondary rear housingsurface and sized specifically to receive a secondary mounting piece1470. For example, the U-groove 1352 may be sized to accommodate a 2×4piece of wood to provide for a more stable and rigid mounting. V-grooveor U-groove 1352 may also be sized and shaped to interface with avariety of other surfaces and/objects, for example, pipes instead of a2×4. Detachable strap 1430 may be detachable from the lateral face ofthe base unit, and able to be pulled around the 2×4 or pipe to holdsecurely during a horizontal or vertical mounting scenario.

FIG. 15 illustrates another embodiment of a base unit 01. In someembodiments, front housing plate 1310 may be segmented into one or morefront housing plate segments, for example, elements 1307 and 1308, eachwhich may be separated by one or more corresponding front housing platevertices 1309. Front housing plate segments 1307, 1308 may be integralwith or abut each other and/or each respective front housing platevertex 1309. One or more pieces of webbing 1372 may be fixedly attachedto any or all of the surfaces, plates, segments, edges, and verticesdescribed herein. In some embodiments, some or all of the webbing 1372may be adapted to be reflective making the base unit 01 easier toidentify. Rear housing plate 1340 may be segmented into one or more rearhousing plate segments, for example, elements 1348 and 1349, each whichmay be separated by one or more corresponding rear housing platevertices 1321. Rear housing plate segments 1348, 1349 may be integralwith or abut each other and/or each respective rear housing plate vertex1321. In various embodiments, each rear housing plate 1340, rear housingplate segment 1348-1349, and/or rear housing plate vertex 1321 may beintegral with, abut, be flush with or offset from, or otherwise bedisposed proximate to each corresponding front housing plate 1310, fronthousing plate segment 1307-1308, and/or front housing plate vertex 1309in accordance with a desired shape or configuration. In variousembodiments, one or more mounting hooks 1373 may each be fixedlyattached to one or more portions of the base unit's housing andconfigured to allow the base unit to hang from an object, for example, ascrew or a nail, or a surface disposed on or around the site beingmonitored. Mounting strap 1371 functions similarly to the mounting strap1371 disclosed in FIGS. 13 and 17.

FIG. 16 depicts a flowchart of one embodiment 1600 of a method fordetermining, by one or more server or controller of the monitoringsystem disclosed herein, an extent to which one or more sites beingmonitored are in compliance with one or more insurance or regulatoryrequirements and/or parameters. The system begins at act 1602. At act1604, the system receives applicable insurance or compliancerequirements associated with a site or sites being monitored. At act1604, the system receives applicable site configuration and/ormonitoring data. At act 1606, the system calculates one or morecompliance grades or thresholds based on the information received duringacts 1602 and 1604. For example, noise levels or vibration levels may besummarized to be reported, or room occupancy data may be summarized tobe reported in accordance with contractor safety programs.

In some embodiments, the system may proceed directly to acts 1614 or1616, or return to act 1602 at a desired interval or schedule, orresponsive to one or more conditions. In other embodiments, the systemproceeds to act 1610 and determines whether one or more grades orthresholds derived in act 1606 has been satisfied to a certain degree.If not, the system may proceed directly to acts 1614 or 1616, or returnsto act 1602 at a desired interval or schedule, or responsive to one ormore conditions. If so, the system proceeds to act 1612 and determineswhether it is time to generate one or more alerts and/or reports basedon the results of act 1610. If not, the system may proceed directly toact 1616 or return to act 1602 at a desired interval or schedule, orresponsive to one or more conditions. If so, the system proceeds to act1614 and generates one or more alerts and/or reports based on theresults of act 1610. For example, the system may generate an reportwhich summarizes the real-time risk over a period of time, an reportdetailing conditions during an installation, or a contractor safetyprogram compliance report. The method finishes at act 1616.

In some embodiments, at some point between acts 1610 and 1616 the systemmay further be configured to save some or all of the informationcollected in acts 1608 and/or 1614 as part of a compliance or riskprofile. The system may save this information in a historical archive ofprofiles for later use. The archived profile information may be accessedagain during act 1604 to inform the subsequent compliance grades orthresholds generated during act 1608, or again at act 1614 to informsubsequent compliance reports.

FIG. 17 illustrates another embodiment of a base unit 01. One or morecavities 356 may be disposed within or underneath a portion of a housingsurface, housing surface segment, housing plate, housing plate segment,edge, vertex, or other exterior portion of a base unit as disclosedherein. A cavity may be removably covered by a hatch, cover, seal, cap,slide door, and/or other closing mechanism 350 known to those in theart. Each cavity 356 may contain one or more sensor interfaces or ports358 for communicatively coupling and/or removably securing a sensor 20or sensor array 424. In some embodiments, unused sensor interfaces 358may be covered by a sensor interface cover 361.

In some embodiments, a plurality of mounting pieces 360 may be ondisposed on a portion of a housing surface, housing surface segment,housing plate, housing plate segment, edge, vertex, or other exteriorportion of a base unit as disclosed herein. For example, the pluralityof mounting pieces 360 may each comprise a magnet and/or adhesive patch.Mounting strap 1371 functions similarly to the mounting strap 1371disclosed in FIGS. 13 and 15, and may further include a releasableand/or adjustable fastener 1374, such as a clip, hook-and-loop fastener,tie, or other such fastening means known to those in the art.

In some embodiments, one or more secondary apertures 314 may be ondisposed on or within a portion of a housing surface, housing surfacesegment, housing plate, housing plate segment, edge, vertex, or otherexterior portion of a base unit as disclosed herein. Any or all of thesecondary apertures 314 may be covered by a grating, webbing, filter,mesh, seal, cover, etc.

Various aspects of the one or more controllers 18 or server 04 may beimplemented as specialized software executing in a general-purposecomputer system 1800 such as that shown in FIG. 18. The computer system1800 may include a processor 1802 connected to one or more memorydevices 1804, such as a disk drive, solid state memory, or other devicefor storing data. Memory 1804 is typically used for storing programs anddata during operation of the computer system 1800. Components ofcomputer system 1800 may be coupled by an interconnection mechanism1806, which may include one or more busses (e.g., between componentsthat are integrated within a same machine) and/or a network (e.g.,between components that reside on separate discrete machines). Theinterconnection mechanism 1806 enables communications (e.g., data,instructions) to be exchanged between system components of system 1800.Computer system 1800 also includes one or more input devices 1808, forexample, a keyboard, mouse, trackball, microphone, touch screen, and oneor more output devices 1810, for example, a printing device, displayscreen, and/or speaker. In addition, computer system 1800 may containone or more interfaces (not shown) that connect computer system 1800 toa communication network in addition or as an alternative to theinterconnection mechanism 1806.

The storage system 1812, shown in greater detail in FIG. 19, typicallyincludes a computer readable and writeable nonvolatile recording medium1902 in which signals are stored that define a program to be executed bythe processor 1802 or information to be processed by the program. Themedium may include, for example, a disk or flash memory. Typically, inoperation, the processor causes data to be read from the nonvolatilerecording medium 1902 into another memory 1904 that allows for fasteraccess to the information by the processor than does the medium 1902.This memory 1904 is typically a volatile, random access memory such as adynamic random access memory (DRAM) or static memory (SRAM). It may belocated in storage system 1812, as shown, or in memory system 1804. Theprocessor 1802 generally manipulates the data within the integratedcircuit memory 1904 and then copies the data to the medium 1902 afterprocessing is completed. A variety of mechanisms are known for managingdata movement between the medium 1902 and the integrated circuit memoryelement 1904, and aspects and embodiments disclosed herein are notlimited thereto. Aspects and embodiments disclosed herein are notlimited to a particular memory system 1804 or storage system 1812.

The computer system may include specially-programmed, special-purposehardware, for example, an application-specific integrated circuit(ASIC). Aspects and embodiments disclosed herein may be implemented insoftware, hardware or firmware, or any combination thereof. Further,such methods, acts, systems, system elements and components thereof maybe implemented as part of the computer system described above or as anindependent component.

Although computer system 1800 is shown by way of example as one type ofcomputer system upon which various aspects and embodiments disclosedherein may be practiced, it should be appreciated that aspects andembodiments disclosed herein are not limited to being implemented on thecomputer system as shown in FIG. 18. Various aspects and embodimentsdisclosed herein may be practiced on one or more computers having adifferent architecture or components that that shown in FIG. 18.

Computer system 1800 may be a general-purpose computer system that isprogrammable using a high-level computer programming language. Computersystem 1800 may be also implemented using specially programmed, specialpurpose hardware. In computer system 1800, processor 1802 is typically acommercially available processor such as the well-known Pentium™, Core™,or Atom™ class processors available from the Intel Corporation. Manyother processors are available, including programmable logiccontrollers. Such a processor usually executes an operating system whichmay be, for example, the Windows 7, Windows 8, or Windows 10 operatingsystem available from the Microsoft Corporation, the MAC OS System Xavailable from Apple Computer, the Solaris Operating System availablefrom Sun Microsystems, or UNIX available from various sources. Manyother operating systems may be used.

The processor and operating system together define a computer platformfor which application programs in high-level programming languages arewritten. It should be understood that the invention is not limited to aparticular computer system platform, processor, operating system, ornetwork. Also, it should be apparent to those skilled in the art thataspects and embodiments disclosed herein are not limited to a specificprogramming language or computer system. Further, it should beappreciated that other appropriate programming languages and otherappropriate computer systems could also be used.

One or more portions of the computer system may be distributed acrossone or more computer systems (not shown) coupled to a communicationsnetwork. These computer systems also may be general-purpose computersystems. For example, various aspects of the invention may bedistributed among one or more computer systems configured to provide aservice (e.g., servers) to one or more client computers, or to performan overall task as part of a distributed system. For example, variousaspects and embodiments disclosed herein may be performed on aclient-server system that includes components distributed among one ormore server systems that perform various functions according to variousaspects and embodiments disclosed herein. These components may beexecutable, intermediate (e.g., IL) or interpreted (e.g., Java) codewhich communicate over a communication network (e.g., the Internet)using a communication protocol (e.g., TCP/IP). In some embodiments oneor more components of the computer system 100 may communicate with oneor more other components over a wireless network, including, forexample, a cellular telephone network.

It should be appreciated that the aspects and embodiments disclosedherein are not limited to executing on any particular system or group ofsystems. Also, it should be appreciated that the aspects and embodimentsdisclosed herein are not limited to any particular distributedarchitecture, network, or communication protocol. Various aspects andembodiments disclosed herein are may be programmed using anobject-oriented programming language, such as SmallTalk, Java, C++, Ada,or C# (C-Sharp). Other object-oriented programming languages may also beused. Alternatively, functional, scripting, and/or logical programminglanguages may be used, for example, ladder logic. Various aspects andembodiments disclosed herein are may be implemented in a non-programmedenvironment (e.g., documents created in HTML, XML or other format that,when viewed in a window of a browser program, render aspects of agraphical-user interface (GUI) or perform other functions). Variousaspects and embodiments disclosed herein may be implemented asprogrammed or non-programmed elements, or any combination thereof.

FIG. 20 depicts an additional embodiment of a base unit configured todetect its orientation and/or perform image processing using one or morecameras 2005 communicatively coupled to the one or more controllers 18within the base unit 01. One or more sensors capable of detectingorientation and/or directional information, such as a magnetic sensor oraccelerometer may be disposed in or communicatively coupled to the baseunit 01 and provide an orientation of the base unit 01. For example, anaccelerometer may use a three-dimensional Cartesian coordinate systemx-y-z to detect a positive or negative force of gravity g acting on oneor more of the axes x, y, and/or z. A magnetic sensor may be furtherconfigured to detect an orientation relative to geographic directionsNorth, South, East, West, up, and/or down. The system may then associatethe appropriate x-y-z directions with corresponding geographicdirections North, South, East, West, up, and/or down. Using theinformation collected by the sensors and the known relationship betweenthe coordinate system and geographic directions, the base unit maydetermine its current orientation.

An additional sensor 20 may have a range or area of detection thatpartially or completely overlaps a range or area of detectioncorresponding to the one or more cameras 2005. For example, an IR sensor20 may have a cone of detection with an angle θ and a camera 2005 mayhave a cone of detection with an angle α. If the IR sensor 20, forexample, detects a sudden change in the thermal distribution within itscone of detection, then the system may be programmed to activate thecamera 2005 in response and perform image processing on the imagescaptured by the camera 2005 in order to identify the object orphenomenon that caused the thermal anomaly. In certain embodiments, thesensors 20 and/or cameras 2005 involved may instead be configured asstandalone external sensors 23 or external peripherals 30, respectively,while still being communicatively coupled to at least one base unit 01.

FIGS. 21A & 21B depict two opposing lateral perspectives of anembodiment of a base unit configured to function as a power pillar 01′.The power pillar 01′ may be configured to receive power from an externalpower supply, for example, from site utility power outlet 2105. Powerpillar 01′ may further comprise one or more power port surface 2113 eachcontaining one or more power ports 2115 for providing power to one ormore external components. Power pillar 01′ may also comprise one or morepower cables 2116 (ending in a male or female power port) for connectingto site power outlets 2105. For example, if the power pillar 01′ cannotbe placed directly adjacent to a site power outlet 2105 then power cable2116 may be used to connect to site power outlet 2105. Power cable 2116may be partially or fully retractable into the body of the power pillar01′. The power pillar 01′ may further comprise one or more backupbatteries and/or UPS devices 2119 for providing backup power toconnected components. For example, battery backups and/or UPS devices2119 may be configured to provide power to one or more connectedcomponents in the event that utility power is unavailable orcompromised.

Power pillar 01′ may also comprise one or more storage cavities 2156,which may each be removably sealed by a hatch 2150 or similar removablesealing apparatus known to those in the art. One or more storage racksor shelves 2110 may be disposed within each storage cavity 2156 and itsposition within the storage cavity may be removable or adjustable. Eachstorage cavity may removably contain one or more system componentsincluding base units 01, sensors 20, 23 or sensor arrays 24, 424,peripherals 30, and/or other system components to be used around thesite being monitored. Storage cavities 2156 and racks 2110 may be used,for example, to removably contain some or all of the equipment to beused at a site when the system is first delivered or to removably storeequipment that was already used at the site following the completion ofmonitoring operations at that site.

Power pillar 01′ may further comprise one or more lights 37 forilluminating the site, indicating an alarm or other status information,or for performing other functions of a light known to those in the art.Power pillar 01′ may also comprise one or more displays 2126 forvisually displaying information, for example, an alarm, site location,or other system or site status information. A display may comprise adigital screen such as an LCD, LED, CRT, OLED, and/or other digitaldisplay device known to those in the art. A display 2126 may alsofunction as a user interface (UI) 26 capable of receiving user input inaddition to displaying information. A display 2126 that is also a UI 26may be a resistive, capacitive, or infrared touchscreen or other userinterface known to those in the art. For example, a user may interactwith the display 2126 by pressing a request icon on the touchscreen andresponsively bring up a map of the site with a status icon indicatingtheir current location within the site.

Example 1

The following is an example of the monitoring system operating inaccordance with an embodiment of the present disclosure.

A construction site consisting of a basement and several above-groundfloors is outfitted with a plurality of base units 01. A number of areaswithin the site contain magnetically-active metal structures and, inthose areas, base units 01 are removably affixed to the structures usingmagnet mounts 360. In other areas, base units 01 are removable affixedto 2×4 pieces of wood via mounting straps 1371. A wireless networkinggateway 32 is disposed near the spatial center of the site and allowsthe base units to wirelessly connect via LPWAN to the gateway 32 andprovides access to a cellular data connection over 3G or 4G. The server04 is hosted on the Internet and may be accessed using the cellular dataconnection.

The controller 18 in each base unit 01 executes a series of instructionscorresponding to the method of networking configuration 1000 (FIG. 10)in order to determine their mode of operation. A number of wirelessrepeaters are also installed around the site in order to extend therange of the gateway 32. Some base units cannot connect directly to thegateway 32 and instead connect to the gateway via one of the repeaters.Several other base units 01 cannot connect to either a gateway orrepeater, but can connect to another base unit acting as a unitqualified to control a local network 01 as depicted in FIG. 10. If thebase unit qualified to control the local network 01 is connected to thegateway 32 or a repeater, then the additional base units connected to it01 may access the cellular network indirectly through the qualified baseunit 01. Otherwise, the local network of base units 01 may operate in anoffline mode temporarily until an outside connection becomes available.

A software platform running on the server 04 collects and analyzes datafrom the connected base units 01 and any external sensors 23, externalsensor arrays 424, or other peripherals 30 connected to any of the baseunits 01. The software platform performs acts 1100 a, 1100 b or 1200followed by act 900 to determine which types of events and/orpreliminary events the system is configured to detect at the site beingmonitored. While performing act 900, a number of temperature sensors ina particular zone plus data from an external weather sensor array 424indicate sub-freezing outdoor temperatures for the next several hours.Based on these readings, it is determined that a preliminary eventcorresponding to a potential frozen and/or bursting water pipe is inprogress. Action 918 is performed, notifying necessary personnel of thepotential for a pipe freezing over the next several hours, and sending acommunication to one of the nearby base units 01 connected via externalperipheral 30 to control a temporary heat source to raise the heatsetting of the temporary heat source. Base unit 01 is further instructedto perform action 920, changing the mode of operation of several sensorsincluding the temperature and humidity sensor to take measurements moreoften and transmit at a higher frequency, and turns ON PIR sensor tobegin looking for detectable temperature profiles.

Several hours later, software platform running on server 04 detects thatsuspected event of a burst pipe (act 922) is causing an ongoing waterleak upon analysis (act 912) of another base unit's 01 sensor data anddespite the aforementioned efforts to prevent and/or delay the event byraising the heat. Act 914 is invoked, sending an alert to necessarypersonnel with details of the location, time, type, and severity of theevent. Personnel may respond and fully contain the event a shortduration thereafter.

Software platform running on server 04 continuously, at discreteintervals, or in response to various conditions performs methods 900,1100, 1200, and/or 1600 and their constituent acts. Once the systemdetects that the event has concluded during the next cycle, the systemgenerates a report detailing the duration, type, location, and severityof the event including the identities of those who receivednotifications and/or alerts.

Separate reports highlighting other parameters may be generated forother entities including insurance providers, owners, or subcontractors.Analysis of reports may provide suggestions for better deployment ofdetection and response measures, such the location of sensor andperipheral placement. For example, the analysis may enhance theplacement of fans and/or temporary heaters for achieving more controlledheat dispersion throughout the building.

In certain embodiments, a base unit may be configured to function as apermanent base unit 01 capable of being permanently installed within thebuilding. In contrast to a removably attached base unit previouslydescribed, a permanent base unit may be intended for long-term servicewithin a building or other monitored site, may be intended to remaininstalled at a monitored site indefinitely or may not be a primarilytemporary installation. A length of long-term service may vary dependingon the nature of the monitored site. In an embodiment, a permanent baseunit may be installed and operate within a monitored site for the lifespan of the monitored site.

Permanent base units 01 may be electrically hard wired to the building'selectrical system, power outlet, or otherwise receive uninterruptedpower. Alternatively, permanent base units 01 may receive power from atemporary source such as a battery. Permanent base units 01 may beinstalled on a wall, inside of the wall, into building materials, in oraround windows, in or around doors, within structural materials, or inor on the building's roof in order to achieve a specific monitoring orsensing purpose. For example, a permanent base unit 01 containingtemperature, humidity, and moisture sensors may be installed within thecavity of a wall to detect mold growth conditions within an occupiedbuilding for the duration of the building's life.

Permanent base units 01 may be similarly configured and constructed tooperate as the removably-attached base unit previously described.However, because of the long-term application of the installation, thepermanent base unit may be capable of performing functions in additionto those performed by the removably-attached base units.

In various embodiments, software running on server 04 may be configuredto communicate with other systems within the building. Software runningon server 04 may be configured to control other systems within thebuilding. Alternatively, software running on server 04 may be configuredto receive inputs from and be controlled by other systems within thebuilding. Other systems within the building may include but are notlimited to the Building Management System (BMS), also known as theBuilding Automation System (BAS), the building Heating, Ventilation, andAir Conditioning (HVAC) system, and the building security system. TheBMS or BAS is installed in a building to control and monitor thebuilding's mechanical and electrical equipment such as ventilation,lighting, power systems, fire systems, security systems, etc.

As depicted in FIG. 22A, permanent base unit 01 may establish a one wayor two way data transmission wirelessly via cell connection 03,Bluetooth connection, or other wireless standards known to those in theart, or via wired connection 2201 directly to building security and/orHVAC system 2202 or to BMS system 2203.

As depicted in FIG. 22A, external sensor modules 23 may be connected viaa mesh network to a permanent base unit 01. A plurality of externalsensor modules 23 and/or external sensor arrays 424 may communicate withone or more permanent base unit(s) 01 using LPWAN, Bluetooth, ZigBee,LF, VHF, UHF, 802.11, Wi-Fi, satellite, cellular network, or otherwireless or wired communication methods or protocols. External sensormodules 23 and/or external sensor arrays 424 may be located in closeproximity to base unit(s) 01 and contain specific sensors or combinationof sensors intended to monitor for specific conditions.

In various embodiments, permanent base unit 01 may be configured tocommunicate with other systems within the building. Permanent base unit01 may be configured to control other systems within the building.Alternatively, permanent base unit 01 may be configured to receiveinputs from and be controlled by other systems within the building.Other systems within the building may include but are not limited to theBuilding Management System (BMS) 2202, also known as the BuildingAutomation System (BAM), the building Heating, Ventilation, and AirConditioning (HVAC) system, and the building security system 2203.

Permanent base units 01 may be configured to act as a building intercomsystem, alert system, or information distribution system. Permanent baseunits 01 may be configured to receive input commands from buildingoccupants via a touch-based interface, LCD interface, other visualinterface, or through a voice recognition system.

Software running on server 04 may be configured to communicate with andreceive information from building occupants, building management, orother software products used by building occupants, including but notlimited to software-based calendars of building occupants installed ondevices that utilize the building's networking system. Software runningon server 04 may intelligently control the BMS in order to improvebuilding energy efficiency or air quality. For example, software runningon server 04 may use information contained in building occupants'calendars to determine what time individual building occupants will bein the building, and where within the building the occupants will be,and intelligently adjust the lighting and HVAC to use less energy whenbuilding occupants are not within a particular section of the building,or within the building as a whole. Software running on server 04 mayintelligently control the BMS in order to prevent damage to thebuilding. For example, software running on server 04 may adjust the HVACheat settings in order to prevent freezing temperatures within thebuilding. In a second example, software running on server 04 may adjustthe HVAC settings to prevent conditions that would lead to mold growth.

Permanent base units 01 may include sensors that enable permanent baseunit 01 to detect room occupancy including but not limited tomicrophones, noise sensors, infrared sensors, passive infrared sensors,or motion detectors. Permanent base units 01 may be configured tofunction as a building security system. Alternatively, permanent baseunits 01 may be configured to function as a complementary addition toanother building security system.

Software platform running on server 04 may be configured to analyze datagathered from permanent base units 01 including temperature, humidity,VOC's, and pressure. Software platforms running on server 04 may befurther configured to assess energy loss within the building. Forexample, a software system running on server 04 may analyze an aggregatedata set gathered from permanent base units 01 and detect that there ishigher energy loss in the form of heat loss from a particular roomwithin the building, floor within the building, or section of thebuilding. Software systems running on server 04 may be furtherconfigured to analyze past and current energy consumption through datagathered from permanent base units 01 and other secondary inputsincluding the BMS and predict future energy consumption based on datacollected and analyzed from secondary inputs including weatherpredictions sourced from internet APIs.

Permanent base unit 01 may have a different design and form factor thanother base units 01. FIG. 23 illustrates one embodiment of permanentbase unit 01, where permanent base unit 01 may include a string ofsensors or a strap with embedded sensors 23, 424. In this embodiment,permanent base unit 01 may be installed around windows to detect waterintrusion, moisture, or temperature variations. Permanent base unit 01may be hard-wired to a power supply 2304 or may be wired through a plugin connection with an electrical outlet. A series of permanent baseunits 01 may be hard-wired or electrically connectable to each other,with each being optionally deployed near or on surrounding or nearbywindows or doors.

FIG. 24 illustrates another embodiment of permanent base unit 01, wherepermanent base unit 01 may be a self-containing sensor module that isfully embedded within wall cavity 2401. As shown, permanent base unit 01may be mounted on an interior surface 526 of a wall in a cavity 2401between wall surfaces and studs that form the wall. In an embodiment, amotion sensor 525 is mounted in the wall and wired to the permanent baseunit 01. It will be understood that any of the aforementioned sensorsmay be attached to permanent base unit 01, such as temperature,moisture, mold, etc. Permanent base unit 01 may be mounted to the wallby means of a mounting bracket 2402. In an embodiment, one or morescrews, bolts, nails, rivets or other mechanical fasteners may be usedto secure the permanent base unit 01 to the wall. Alternatively, otherattachment means may be utilized including, but not limited toadhesives, caulk, silicone, strapping or other suitable attachment meansmay be used.

FIG. 25A illustrates another embodiment of permanent base unit 01, wherepermanent base unit 01 may be mounted on the exterior portion of aninterior wall 2501 within a room of a building. Permanent base unit 01may collect sensor readings from within the room itself. Externalsensors 23 may be mounted within wall cavity 2502. Permanent base unit01 may be hard wired via wiring 2503 to external sensors including butnot limited to external sensors 23, moisture sensor 525 and temperatureand humidity sensors located within the wall cavity 2502. Permanent baseunit 01, as well as sensors 23, 525, may be mounted to the wall surfacesby mechanical fasteners 2505 or by other means, as described above.Alternatively, sensor 525 may be mounted to wall surface 526 throughprongs 628 with or without the addition of an adhesive or other securingmeans.

FIG. 25B illustrates another embodiment of permanent base unit 01, wherepermanent base unit 01 may be mounted on the exterior portion of aninterior wall 2501 within a room of a building. Permanent base unit 01may collect sensor readings from within the room itself. Externalsensors 23 may be integral with an exterior portion of permanent baseunit 01 such that the sensor extends into the wall cavity 2502.Permanent base unit 01 may be hard wired via wiring 2503 to externalsensors including but not limited to moisture sensor 525 and temperatureand humidity sensors located within the wall cavity 2502.

FIG. 26 is a flowchart that depicts one embodiment 2600 of a method ofthe analytic portion of a monitoring system as disclosed hereinperforming event prediction and response at one or more sites beingmonitored by the monitoring system. Event prediction and response method2600 is similar to event prediction and response method 900 of FIG. 9,but includes further operation features, acts 2607-2609, that may beperformed by a permanent base unit 01 the present disclosure.

Event prediction and response method 2600 begins at act 2602 andinvolves act 2604, receiving information and/or accessing the locations,types, and other properties of the one or more sensors connected to orinstalled in the one or more base units 01 at the site being monitored.The system further receives information describing characteristics ofthe site itself, including site physical layout and/or dimensions, siteenvironmental conditions including location, climate, or weather,selected site preferences including worker condition thresholds, andcurrent and historical data trends, customer imposed thresholds,micro-weather station data, and/or other site environmental parameters.At act 2605, the system determines plausible events or preliminaryevents that are detectable at the given site based on the informationreceived at act 2604. At act 2606, the analytic system receives and/oraccesses data tailored to the specific configuration of the present siteor sites being monitored based on the data received and/or accessed.

The system may maintain one or more databases of previous monitoring andresponse operations conducted at different sites including the types andlocations of various equipment deployed at the site and informationsurrounding events, preliminary events, and/or other actions that werelogged at that site. The system may be further configured to storeadditional information in a database including site configurations andstatuses at different times, environmental statuses (for example ambientweather conditions) at different times, base unit configurations andstatuses at different times, sensor configurations and statuses atdifferent times, and/or event statuses at different times. This databasemay be used in connection with any of the data lookup or comparisonfunctions performed within the scope of this disclosure. For example,the system may associate a present site with one or more previous sitescontaining a similar physical and/or environmental layout and similarbase unit and/or sensor configuration, and predict, based on events thatwere detected at the previous sites, one or more events that are morelikely to occur at the current site. Such predictions may enhancemonitoring and/or response operations at the current site by putting thesystem and/or system users on notice of elevated sources of risk. Suchassociations may also assist system users in setting up operations at anew site and/or reconfiguring operations at an existing site. Forexample, the database associations may assist system users in selectingthe number, type, location, and/or operating mode of one or more baseunits 01, sensors and sensor arrays 20, 23, 24, 424, peripherals 30,and/or other connected system components.

Act 2606 may further include generating a model of the site or sitesbased on the information received in acts 2604-2606. In one embodiment,the tailored data is received and/or accessed pursuant to one of thedatabase selection methods depicted in FIGS. 11A-11B, however theanalytic system may receive and/or access data used to perform eventprediction via an alternate method or source.

At act 2607, the system may receive information from the building'sBuilding Management System. As described above, this information mayinclude information regarding the building's mechanical and electricalequipment such as ventilation, lighting, power systems, fire systems,security systems, etc., as well as operational requirements of thebuilding for these systems. At act 2608, the system may receiveinformation available from software-based calendars of occupants of thebuilding. This may enable the system to alter certain operations withinthe building based on occupancy and scheduling information gathered inthis act. In act 2609, the system may receive information from thebuilding security system. Such information may include informationregarding high-security portions of the building, portions of thebuilding that are only accessible by occupants with special clearances,information regarding the status of security gates, door and or windows,fire system information and other relevant information.

At act 2610, the analytic system uses the site configuration datareceived and/or accessed during act 904, the tailored data receivedand/or accessed during act 2606 and the BMS, calendar and securityinformation received during acts 2607-2609 to determine one or moreparameter thresholds corresponding to one or more events and/orpreliminary events. A preliminary event may be an event that may beindicative of a potential or imminent occurrence of an undesirable orimportant event. For example, a preliminary event may be an increase intemperature beyond a certain threshold, which may be indicative of anincreased likelihood of a possible fire. In some embodiments, an eventor preliminary event may be indicated by a plurality of parameterthresholds instead of a single parameter threshold.

At act 2611, the analytic system receives monitoring data from the oneor more sensors at the one or more sites. At act 2612, the systemcompares the data received during the previous step to the parameterthresholds determined during act 908 to determine whether an event is inprogress. The analytic system may comprise a memory that storesassociations between certain types or configurations of parameterthresholds and certain events and, in some embodiments, preliminaryevents.

In some embodiments, the event prediction and response system 2600further comprises the ability to detect preliminary or suspected events.If an event is not detected, the system proceeds to act 2616 todetermine whether a preliminary event is in progress based on storedassociations between monitoring data and various preliminary eventtypes. If a preliminary event is not detected, the system resets,pauses, repeats or otherwise continues with its current programmingdepending on the desired embodiment. If the system detects a preliminaryevent, at act 2618 the system may issue a preliminary event alert and/ortake responsive action. For example, in some embodiments the system maybe coupled to one or more actuators 30 capable of controlling theoperating mode of one or more fans disposed near one or more heaters atthe site being monitored. If a preliminary event is detected suggestingthat cold conditions are approaching, then at act 2618 the system maytake proactive/corrective action by controlling the one or moreactuators 30 to turn ON or increase the speed of the one or more fanslocated near the heaters in order to disperse heat at the site moreeffectively. A preliminary event alert may comprise any form of alert,notification, or communication with an external user or entity, forexample, mobile user 05, desktop user 06, or other type of user orentity.

In some additional embodiments, at act 2620 the system may activelymonitor and/or change the configuration, power, or other settings of oneor more sensors and/or related components and systems. In addition tostoring associations between certain types or configurations ofparameter thresholds and certain preliminary events, analytic system mayalso store associations between certain preliminary events and certainevents. The analytic system may store additional associations betweencertain parameter thresholds and certain events responsive to the one ormore events being associated with the preliminary event at issue. Usingthese associations, the analytic system can alter the programming of themonitoring system to prioritize detection of the associated events. Insome embodiments, the system may also use the associations to performadditional or different response measures at the one or more sites beingmonitored.

In one embodiment, detecting a preliminary or suspected event 2616involves using one or more infrared sensors to map a gradient ofinfrared light intensity, power, energy, or a related property.Responsive to one or more infrared light properties meeting or exceedingone or more thresholds the determination that a preliminary event hasoccurred can be made and a preliminary alert or responsive action may beissued (act 2618) corresponding to the type of preliminary eventinvolved.

At act 2620, the system may change an operating mode or characteristicof one or more base units, servers, handsets, sensors, actuators, and/orother system components responsive to the detection of a preliminaryevent during act 2616. For example, the system may change the frequencyat which the central controller and/or base unit reads or analyzessensor data. In some embodiments, the system may change the frequency atwhich a sensor or sensors receive or transmit new data, or theconditions under which a sensor or sensors receive or transmit new data.In other embodiments, the system may change the power drawn by one ormore base units or other system components. In other embodiments, thesystem may toggle whether one or more system components are in an ONstate versus an OFF state. For example, if a preliminary eventindicating a heightened risk of fire is detected, the system mayactivate, increase the refresh frequency of, or increase the powerprovided to one or more base units and/or sensors associated with firedetection.

In some embodiments, taking responsive action during acts 2614 and/or2618 involves communicatively coupling one or more actuators,controllers, or other peripheral devices 30 to one or more base units.Each peripheral may be coupled to one or more objects, devices, orsystems at the site or sites being monitored and may be configured tocontrol one or more aspects of operation responsive to an eventdetermination made during act 2612 or a preliminary event determinationmade during acts 2616, 2620, and/or 2622. For example, a base unit maybe communicatively coupled to a valve actuator disposed in a fluid pipeand configured to control the operation of said valve responsive todetection of a fire event. Said actuators may be disposed within a baseunit or outside of a base unit depending on the desired configurationand type of actuator. Base units may be further configured to controlthe operation of various types of on-site equipment including lighting,fans, heating, humidifiers, dehumidifiers, and/or other controllableequipment or fixtures disposed in, on, or around the site(s) beingmonitored.

In other embodiments, taking a responsive action at acts 2614 and/or2618 involves automatically taking corrective or preventive action toensure that damage or risk from an event is minimized or avoidedaltogether. For example, if a motion sensor detects an event orpreliminary event corresponding to a suspected intruder, the system maybe automatically configured to activate one or more lights around thesite to deter or scare off the intruder prior to initiating a full alarmor other response. In another example, if a temperature sensor detects afrozen pipe, the system may be automatically configured to determinewhether increasing the operation of one or more heaters would besufficient to unfreeze the pipe and initiate the necessary operation ofsaid heaters in response.

In various embodiments, the system may generate a printed, audiovisual,or partially printed and partially audiovisual report responsive to thedetection, suspicion, and/or conclusion of an event and/or preliminaryevent. An example of a hybrid printed-audiovisual report is depicted inFIG. 8. The generation of such a report may occur during each or any ofacts 2602-2624.

FIG. 27 is a flowchart of an embodiment 2700 of a method of the analyticportion of a monitoring system as disclosed herein performing eventprediction and response at one or more sites being monitored by themonitoring system. While this example is directed to a particularstandard concerning a particular environmental situation that is to bemonitored, it will be understood that this process may be applicable toany number of operating characteristics that may be monitored.

Event prediction and response method 2700 begins at act 2702 andinvolves act 2704—receiving information regarding various compliancestandards, such as LEEDS, for example, with which a building managementmust comply. The system then receives various information collected byone or more permanent base units 01 associated with the building fromvarious monitored sites, as well as information describingcharacteristics of the site itself, including, but not limited to, sitephysical layout and/or dimensions, site environmental conditionsincluding location, climate, or weather, selected site preferencesincluding occupant condition thresholds, and current and historical datatrends, occupant imposed thresholds, micro-weather station data, and/orother site environmental parameters, act 2706. In this example, at act2708, the system determines the energy loss through analyzing andcomparing environmental conditions exterior to the building withenvironmental conditions interior to the building, BMS configurations,and expected energy transfer rates. At act 2710, the system determinesif there is significant energy loss to the extent that any LEEDstandards, for example, have been violated. If not, the system returnsto act 2702 to continue the monitoring process. If the result of act2710 is “yes,” at act 2712, the system determines whether if a reportof, in this example, energy efficiency has been requested. If “yes,” atact 2714, the system generates a report based off the informationcollected in acts 2704 through 2708. Otherwise, the system returns toact 2702 to continue the monitoring process.

Having thus described several aspects of at least one embodiment of thisinvention, it is to be appreciated various alterations, modifications,and improvements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis disclosure, and are intended to be within the spirit and scope ofthe invention. Accordingly, the foregoing description and drawings areby way of example only.

What is claimed is:
 1. A site monitoring system comprising: a base unitconfigured to be mounted to a structure of a monitored site; at leastone sensor configured to monitor at least one monitored site condition;and a controller disposed within the base unit, the controllerconfigured to receive sensor information regarding the at least onemonitored site condition from the at least one sensor and to receiveoperation information from at least one monitored site managementsystem; the controller configured to process the sensor information andthe operation information against predetermined monitored siteparameters and to provide control instructions to the at least onemonitored site management system to affect the at least one monitoredsite condition. 2.-36. (canceled)